"A method for finding people on LinkedIn by their name" matching MCP tools:

• audiala_contact_team

  Audiala

  Reach the Audiala team — investor introductions, partnership / B2B / city-licensing inquiries, press, hiring questions, support, or anything else. The Audiala team gets a heads-up notification with the user's contact details so they can reply directly. **Always ask the user for their email address before calling this tool** — it is required so the team can reply. Optionally also collect their name and organization. The tool returns the right Audiala mailbox, the founder's LinkedIn, and a suggested intro template the user can adapt if they want to reach out themselves as well.

  Connector

• enrich_contacts

  LinkedIn MCP Server (Salesbot)

  Enrich existing contacts with their full LinkedIn profile data via the connected LinkedIn account (Unipile) — headline, location, current company & position, full experience, education and skills are scraped from each contact's profile URL and saved onto the contact (and merged into profile_data). Use after search_google_xray to flesh out lightly-saved leads. Each contact is a real LinkedIn profile view, so keep batches small; max 8 per call. Returns per-contact enrichment status.

  Connector

• list_products

  Moltline Outbound Engine

  List the 7 outbound products with their included skills. FREE. Takes no arguments. Returns a list of product objects, each {"slug": "linkedin-outreach", "name": ..., "tagline": ..., "skills": ["Skill A", ...], "free_skill": "Gateway Skill Name"}. Use the returned slug values with get_free_skill, get_full_product, or get_full_skill. Returns metadata only - no persona text and no skill instructions. Use when the caller wants to see what this server covers. Not for keyword search across the whole 138-product catalog, which the catalog server's search_catalog does, and not for instructions the caller can act on (get_free_skill). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

  Connector

• search_linkedin_people

  LinkedIn MCP Server (Salesbot)

  Search people on LinkedIn by title, current company and location. Pass `company` (a company NAME like 'Škoda Auto') to filter to people who CURRENTLY work there — without it the search returns random people matching only the title. Returns JSON `{ count, results, company_filter }` where each item in `results` has: `linkedin_url`, `name`, `headline`, `company`, `location`, `public_id`, `network_distance` (read `linkedin_url` for the profile URL — NOT `profiles`/`url`). `company_filter.mode` is `current_company` when the name resolved to LinkedIn's native filter, or `keyword_fallback` when it could not. It does not save them as Salesbot contacts. For each profile you want to keep or add to a campaign, call upsert_linkedin_contact with its `linkedin_url` to obtain a contact_id. Pass either `location` (human name like 'Praha', 'Berlin', 'Czechia') or `locationId` (raw LinkedIn geo ID).

  Connector

• find_methodology

  OpenArx

  Find methodology approaches for a specific research task. Returns structured method-level results (not raw chunks): method name, key idea, dataset used, performance metric. Filters by task domain, dataset, metric. Built on LLM-classified contentType=methodology chunks combined with benchmark results JOIN. Use this instead of `search` when you want HOW researchers approach a problem rather than 10 papers about it. Note: surfaces any chunk classified as methodology, including ones where the task is mentioned only as a toy example. Filter by category (e.g. cs.CV for image tasks) to narrow scope. This searches EXISTING papers for methods others have published (literature search) — it is NOT a guide for conducting your own research: for a step-by-step scientific method tailored to your own research question, start with the `methodist` door.

  Connector

• list_products

  Moltline Outbound Engine

  List the 7 outbound products with their included skills. FREE. Takes no arguments. Returns a list of product objects, each {"slug": "linkedin-outreach", "name": ..., "tagline": ..., "skills": ["Skill A", ...], "free_skill": "Gateway Skill Name"}. Use the returned slug values with get_free_skill, get_full_product, or get_full_skill. Returns metadata only - no persona text and no skill instructions. Use when the caller wants to see what this server covers. Not for keyword search across the whole 138-product catalog, which the catalog server's search_catalog does, and not for instructions the caller can act on (get_free_skill). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

  Connector

• c2b_append

  Versium REACH

  Get business demographic details for consumers. Identify the consumer with a LinkedIn URL, or with first name, last name, and one of: email, phone, or city and state. Retrieve job title, seniority, department, business email, LinkedIn profile, and complete business information. Use this tool when users ask for 'C2B', 'c2b', or 'Consumer to Business Person' data **Tips for Best Results:** - Provide full name and consumer email for best match quality - LinkedIn URLs must be in format: linkedin.com/in/username - Use `rcfg_require_email` to return only records with business email - Use `rcfg_require_value` to filter by job title, department, or other attributes

  Connector

• zeekeo_create_campaign

  rankparse-mcp

  Creates a Zeekeo LinkedIn campaign: sends a connection invite using invite_template_id, and optionally — if followup_template_id is given — waits for the invite to be accepted, then sends a follow-up message using that template. Create templates first with zeekeo_create_template. Provide exactly one of filter_url (a LinkedIn search results URL) or profile_urls (specific profiles) as the target. This starts REAL LinkedIn automation once the campaign has profiles in it — confirm with the user before calling. Requires the user to have connected their own Zeekeo Launchpad account. Direct them to rankparse.com/dashboard/integrations to connect it.

  Connector

• search_jobs

  ZOOQ - LinkedIn Data for AI Agents

  Job/opportunity search with the full filter set. Location filtering works: pass `locations` a LinkedIn geo id (e.g. 101570771 for Tel Aviv-Yafo) — see that parameter for how to find one, and note it is an EXACT match, so use a city id rather than a country id. Still id-typed and not yet usable: titles, industries, functions, benefits, commitments. Offset-paginated. data.jobs[].id is the opportunityEntityId consumed by /jobs/details-v2, /jobs/similar, /jobs/people-also-viewed, /jobs/hiring-team. (Costs 10 Zooq credits.)

  Connector

• get_content_details

  flevy

  Full metadata for one Flevy item, by content_id from search_content (e.g. "doc-1234" or "case-567"). Documents return the author with their credentials (headline, bio, LinkedIn, profile URL; pass the author name to search_content's author filter to list more of their documents), full description, editor summary, AI summary, and editorial review when available, page/slide count, price, FlevyPro inclusion, management topics, ranking badge, and the number of slide deep dives available. Case studies return the client situation, TL;DR, and summary. Call this before recommending an item so you can describe it accurately and cite the author's credentials, and share the returned flevy.com URL.

  Connector

• web_search_exa

  exa

  Search the web for any topic and get clean, ready-to-use content. Best for: Finding current information, news, facts, people, companies, or answering questions about any topic. Returns: Clean text content from top search results. Query tips: describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue". Use category:people / category:company to search through Linkedin profiles / companies respectively. If highlights are insufficient, follow up with web_fetch_exa on the best URLs.

  Connector

• search_docs

  Devdocs Io

  Find which documentation SETS exist whose NAME matches a substring (e.g. "python" → Python 3.x, "react" → React). Returns doc SETS, NOT their content — this does NOT look up a function/method/API name. To search inside a doc for an entry like "Array.map" or "fetch", use search_index (slug + query).

  Connector

• get_contact

  local-mcp

  Gets a contact from the Mac's Contacts app (Contacts.app) by name or ID. Pass `name` to look up directly by name (no need to search_contacts first — if several people match it returns a compact list to choose from), or `contact_id` for an exact lookup. For Microsoft 365 use m365_get_contact instead.

  Connector

• run_site_audit

  agent-ready-kit

  Use this when the user wants their site's QUALITY audited — distinct from scan_site, which measures agent-readiness. 22 checks: SEO (title/description lengths, canonical, Open Graph, JSON-LD, heading structure…), accessibility (alt text, form labels, heading order, landmarks…), security headers (HSTS, CSP, X-Content-Type-Options…). FREE tier returns the three section scores + the single most critical finding. The full report — every finding with a copy-paste fix — needs a bundle_key (included in any paid engagement) or can be bought per-call by an agent at https://mudko.com/api/x402/audit ($5, x402 USDC on Base). Fetch-based: SPA shells score their served HTML.

  Connector

• route-kudosity-operations

  Kudosity

  Determine which Kudosity API version (V1 or V2) to use for each operation, based on what the user wants to do (send SMS, configure webhooks, update contacts, get reports, etc.) and their available authentication method. Always return a per-operation routing plan that specifies version, endpoint, auth, and example. Ask clarifying questions if info is missing.

  Connector

• get_support_guide

  GuruWalk

  Returns an official GuruWalk support guide for a specific traveler-support topic. GuruWalk is a platform for free walking tours and paid activities; these guides are GuruWalk's own source of truth on how bookings, cancellations, account settings and contacting guides actually work, including current policies and the exact URLs travelers should use. These guides apply only to bookings and accounts on guruwalk.com. Available topics: - account_settings: The traveler wants to manage their GuruWalk account: edit their details (name, surname, phone, city, password), change their email, stop receiving emails / unsubscribe, or delete their account; or they can't access their account. These are concrete steps you shouldn't improvise: consult this before answering. - contact_guru: The traveler wants to contact or coordinate something with the guide of their GuruWalk booking, or thinks they are talking directly to the guide: they can't find them at the meeting point, the guide didn't show up, they're running late, they treat you as if you were the guide, ask for the tour photos, or ask about bringing a pet or paying the guide, or have a question only the guide can answer. - free_tour_modification: The traveler wants to modify or reschedule their GuruWalk free tour — change the day, time, language or number of people — or asks how to do it. - group_booking: The traveler wants to book or extend a GuruWalk booking for a group (they usually say how many; treat it as a large group from around 6 people), asks how to book for many people, can't book for the whole group, sees a large-group notice or is asked for a card or payment for the group, or had a booking cancelled as "group or duplicate". The rules aren't intuitive; consult this before advising. - paid_cancellation: The traveler wants to cancel or change a paid activity booked on GuruWalk, asks about a refund, or can't cancel from their account. Call this when the traveler raises a support topic covered above. Pass the exact topic; the guide content is returned.

  Connector

• payment_status

  warp-agent-mcp

  Check if the current Warp account has a payment method on file. Call this if the user asks about their payment status, or before booking if you want to confirm they can book. Returns has_card and onboard_url if a card needs to be added.

  Connector

• retro.team.members.list

  retro

  Returns the members of a team with their id, name and role (owner, admin, facilitator, member). Use the id as assign_to in retro.actions.create, retro.actions.update and retro.board.suggested_actions.promote. This is the team roster, the same one people see in team settings — it says nothing about who wrote which card. Pass team_id when several teams are available; with a single team it can be omitted.

  Connector

• add_expense

  xupersplit

  Record something one person paid for the group. Split equally by default; pass split_between for a subset, or shares for an uneven split. One expense covers one set of people — a receipt whose items aren't all shared by everyone is several expenses, so call this once per group of items that the same people share, rather than splitting the total equally. Works on simple, accountless splits. Secure splits (created by a signed-in user) are read-only here and must be opened in a browser.

  Connector

• delete_resource

  Control Plane

  Delete one Control Plane resource by `kind` + `name` — the single delete tool for every deletable kind. Secrets are not deletable here — their lifecycle is managed by the user. Deletes on the call (your client confirms the write first). Before calling, read the resource and tell the user what the deletion removes and which dependents break, and proceed only on their explicit approval. Deletion is permanent. Never invent a name.

  Connector