NestDaddy

Linkedin Buying Signals

com.getcleed/linkedin-buying-signals · v1.1.0

Find B2B prospects showing buying signals on LinkedIn and draft the outreach.

Connect Remote server

Terminal
claude mcp add --transport http linkedin-buying-signals https://www.getcleed.com/api/mcp
~/.cursor/mcp.json
{
  "mcpServers": {
    "linkedin-buying-signals": {
      "url": "https://www.getcleed.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "linkedin-buying-signals": {
      "type": "http",
      "url": "https://www.getcleed.com/api/mcp"
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://www.getcleed.com/api/mcp

Tools 38 found in our last check

  • get_sample_pipeline

    A fictional pipeline in exactly the shapes the real tools return: an ICP, the signal definitions, pipeline stats and six prospects with their signals, verbatim quotes and drafts. Works without any credential, so an agent can show what Getcleed produces before an account exists.…

  • list_prospects

    Search the saved prospects in the account. Filter by company, industry, job title, country, signal type, minimum number of signals, whether an email address is known, enrichment state, or whether they have been contacted. Ordered by signal count, then most recently saved.

  • get_prospect

    Everything known about one prospect: role, company, location, language, every detected signal with the verbatim quote from its source and the LinkedIn URL it came from, any existing email or LinkedIn draft, and outreach state.

  • get_pipeline_stats

    How the pipeline stands: how many prospects, how many carry signals, enrichment state, how many have an email address, how many were contacted, what was added in the last 7 days, the most common signal types, and the remaining plan quota.

  • list_signals

    The buying signals this account looks for: the predefined ones and the custom ones, each with the definition used to detect it and whether it is enabled. Use the returned type values with list_prospects and find_leads_from_signals.

  • get_icp

    The active targeting (ICP): target roles, industries, countries, company sizes, relevant keywords and every saved exclusion. This is what find_leads searches for and what scoring filters against. Change it with update_targeting, add_exclusion and remove_exclusion.

  • add_leads_from_urls

    Save LinkedIn profiles as prospects and enrich them (name, role, company, industry, location, language). Skips anyone already saved. Counts against the import quota.

  • find_leads_from_signals

    Search recent LinkedIn posts on the topics of this account's own signal definitions, keep only posts a check can prove are on topic, and return the people who wrote, commented on or reacted to them, filtered against the ICP (role, industry, country) and ranked. Nothing is saved:…

  • import_sourced_leads

    Save candidates returned by find_leads_from_signals. They arrive already enriched and with the signal attached, including the verbatim quote from the post that surfaced them. Counts against the import quota.

  • analyze_prospects

    Run the signal pipeline on prospects: enrich anyone missing company data, read their recent LinkedIn activity, and detect buying signals. Every signal kept must quote its source verbatim. Counts against the monthly analysis quota. Slow: expect up to a few minutes.

  • draft_email

    Write a personalised email for a prospect, built from their detected signals, in their language. Saves the draft on the prospect and returns it. Does not send.

  • draft_linkedin_message

    Write a short LinkedIn connection note for a prospect from their detected signals, in their language. Saves the draft and returns it. Does not send. Drafts follow the house rules (one fact about them, one question, no pitch, under 200 characters) and so must any note passed to s…

  • send_email

    Send an email to a prospect from the connected mailbox. This reaches a real person immediately and cannot be undone. Pass the subject and body you want sent, or omit them to send the saved draft. Requires a mailbox connected in getcleed under Integrations.

  • send_linkedin_message

    Send a LinkedIn connection request with a note to a prospect from the connected LinkedIn account. This reaches a real person immediately and cannot be undone. Pass the note you want sent, or omit it to use the saved draft. Requires LinkedIn connected in getcleed under Integratio…

  • mark_email_sent

    Record that a prospect was emailed outside getcleed, so reporting and follow-ups stay correct.

  • create_custom_signal

    Teach the account a new buying signal to look for, described in plain language (for example "people complaining their onboarding takes too long"). Future analyses and sourcing will use it.

  • find_leads

    Search for new people matching the account targeting (see get_icp; change it with update_targeting or add_exclusion first if the user wants someone else). Runs in the background for two to five minutes and puts the people found in the review queue: nobody is saved until approve_…

  • get_search_status

    Whether a find_leads search is running or finished, how many people are waiting in the review queue per search, and the weekly discovery allowance left.

  • list_search_results

    People found by searches, best fit first. "to_review" is the queue waiting for a decision, "approved" the ones saved as leads, "rejected" the ones marked not a fit (they can be restored with reject_leads undo). Each person has a fit level against the targeting and the reason for…

  • approve_leads

    Save people from the review queue as leads (in a list named after their search), and optionally add them to a sequence. Pass ids from one search, or a searchId to approve everyone still waiting in it. If the sequence is running, the first call returns what will be sent and needs…

  • reject_leads

    Mark people in the review queue as not a fit, optionally with the reason. They leave the queue and later searches skip them. With undo: true, brings rejected people back to the queue. When the reason would apply to others too, offer add_exclusion.

  • update_targeting

    Change who find_leads looks for: target job titles, industries, countries and company sizes. Each field passed replaces that field; fields left out stay as they are. Show the user the current targeting (get_icp) and the change before calling. To exclude people, use add_exclusion…

  • add_exclusion

    Save an exclusion in the account targeting so later searches skip matching people: a job title keyword, an industry, or a company size limit. With candidateId (a result just rejected), matching people still waiting in that same search are removed too. The user can see and remove…

  • remove_exclusion

    Take one saved exclusion out of the account targeting. Pass it as get_icp lists it under exclusions.

  • list_sequences

    Every outreach sequence in the account: whether it is running, whether each message is reviewed before sending, its steps in short, and how many leads are in each state.

  • get_sequence

    One sequence in full: its steps, its sections (the search each group of leads came from, which can be stopped or resumed on its own), and each lead with where they are, what happens next and when.

  • create_sequence

    Create an outreach sequence. approach "signal": a connection request, then an opener Getcleed writes for each lead from their own signals and two follow-ups (the default, and what the product is for). "simple": four short generic messages. "own": fixed messages you pass, sent to…

  • add_leads_to_sequence

    Put saved leads (prospect ids from list_prospects) into a sequence. Leads already in a sequence, dismissed, or who replied are skipped. If the sequence is running, the first call returns what will be sent and needs confirm: true. Without LinkedIn connected and a sending schedule…

  • start_sequence

    Start a sequence: its leads are enrolled and steps begin going out on the sending schedule, from the user's own LinkedIn account. The first call returns how many people it reaches and whether messages are reviewed first; it only starts with confirm: true. With section, resumes j…

  • stop_sequence

    Stop a running sequence: nothing more is sent until it is started again. With section, stops only the leads that came from that search and leaves the rest running. Stopping never unsends anything.

  • list_sequence_messages

    For each lead in a sequence, the messages still to be sent to them, with the text when it is already written, and the evidence about the lead the text is based on. Use it to show the user what will go out, and before approving a message when review is on (pass the evidenceFinger…

  • update_sequence_lead

    Act on one lead inside a sequence (enrollmentId from get_sequence or list_sequence_messages). editText rewrites a message not sent yet. status "active" approves the waiting message when review is on (pass the evidenceFingerprint that list_sequence_messages returned with the text…

  • list_replies

    Conversations where a lead answered the outreach and the user has not replied yet, newest first, on LinkedIn and by email. Use the id and channel with get_conversation and send_reply.

  • get_conversation

    The messages of one conversation with a lead, oldest first, each marked as written by the user or by the lead. Read it before writing a reply.

  • send_reply

    Send a reply in a conversation, from the user's own LinkedIn account or mailbox. It reaches the lead immediately and cannot be undone: show the user the exact text and get their agreement first. Only conversations started by Getcleed outreach can be answered here.

  • get_account_status

    Where the account stands: plan and allowances, whether the targeting exists, whether LinkedIn and a mailbox are connected, the sending schedule, and the next steps the product suggests. Steps that need a browser (connecting LinkedIn or a mailbox, billing) come with the link to g…

  • update_sending_settings

    When and how fast sequences send: time zone, days, hours, daily limits, and whether sending is on at all. Fields left out keep their value. Turning it on lets running sequences send: that first call returns the schedule and needs confirm: true, and the first time it also needs t…

  • set_lead_status

    Dismiss saved leads (prospect ids from list_prospects): no more outreach goes to them and any sequence they are in is paused for them. "restored" brings dismissed leads back.

Details

Endpointhttps://www.getcleed.com/api/mcp (Streamable HTTP)
First published25 Sep 2026
Last updated25 Sep 2026
Registry namecom.getcleed/linkedin-buying-signals

More marketing and seo servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.