Skip to the content
getcleed
Book a demoStart free

MCP server

Run your outbound from Claude

Connect Claude to Getcleed with one line, then just ask. It reads your buying signals, finds and imports new leads, drafts the outreach and sends it. 38 tools, no code.

Connect in one line

Either approve the connection once in Getcleed (OAuth, nothing to copy), or paste an API key from Settings, Integrations, Developer API, where the “Use in Claude” tab fills the line for you.

Not signed in yet? Getcleed asks you to log in or create an account, then brings you straight back to the approval screen. The connection is created on any plan; the tools start working once the 7-day free trial starts, with nothing to reconnect.

With OAuth, nothing to copy (recommended)

The client registers itself and sends you to a Getcleed screen to approve. You can grant read-only access if you prefer.

claude mcp add --transport http getcleed https://www.getcleed.com/api/mcp

Claude Code, with an API key

claude mcp add --transport http getcleed https://www.getcleed.com/api/mcp --header "Authorization: Bearer YOUR_API_KEY"

Claude Desktop, or any client that only takes a URL

https://www.getcleed.com/api/mcp/YOUR_API_KEY

Server: https://www.getcleed.com/api/mcp (streamable HTTP). Without a key it still answers initialize, tools/list and get_sample_pipeline, a fictional pipeline in the real shapes, so an agent can read what Getcleed does and show you what it produces before you have an account.

Then just ask

  • “Find new leads for me and show me the best ones to approve.”
  • “Reject everyone from agencies in that list and stop showing me agencies.”
  • “Create a sequence for the leads I just approved and show me the first messages before it starts.”
  • “Who replied this week? Draft an answer for each and send the ones I approve.”
  • “Which of my leads showed a buying signal this week?”
  • “What is left to set up on my account?”

What Claude can do

Try it, no account needed

  • 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.

Account and setup

  • 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.
  • update_sending_settings When and how fast sequences send: time zone, days, hours, daily limits, and whether sending is on at all.

Targeting

  • get_icp The active targeting (ICP): target roles, industries, countries, company sizes, relevant keywords and every saved exclusion.
  • update_targeting Change who find_leads looks for: target job titles, industries, countries and company sizes.
  • 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.
  • remove_exclusion Take one saved exclusion out of the account targeting.
  • 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.
  • 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").

Find and review leads

  • 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).
  • 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.
  • approve_leads Save people from the review queue as leads (in a list named after their search), and optionally add them to a sequence.
  • reject_leads Mark people in the review queue as not a fit, optionally with the reason.
  • add_leads_from_urls Save LinkedIn profiles as prospects and enrich them (name, role, company, industry, location, language).
  • 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.
  • import_sourced_leads Save candidates returned by find_leads_from_signals.

Read the pipeline

  • list_prospects Search the saved prospects in the account.
  • 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..
  • analyze_prospects Run the signal pipeline on prospects: enrich anyone missing company data, read their recent LinkedIn activity, and detect buying signals.
  • 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.

Sequences

  • 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.
  • add_leads_to_sequence Put saved leads (prospect ids from list_prospects) into a sequence.
  • 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.
  • stop_sequence Stop a running sequence: nothing more is sent until it is started again.
  • 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.
  • update_sequence_lead Act on one lead inside a sequence (enrollmentId from get_sequence or list_sequence_messages).

Replies

  • list_replies Conversations where a lead answered the outreach and the user has not replied yet, newest first, on LinkedIn and by email.
  • get_conversation The messages of one conversation with a lead, oldest first, each marked as written by the user or by the lead.
  • send_reply Send a reply in a conversation, from the user's own LinkedIn account or mailbox.

One-off outreach

  • draft_email Write a personalised email for a prospect, built from their detected signals, in their language.
  • draft_linkedin_message Write a short LinkedIn connection note for a prospect from their detected signals, in their language.
  • send_email Send an email to a prospect from the connected mailbox.
  • send_linkedin_message Send a LinkedIn connection request with a note to a prospect from the connected LinkedIn account.
  • mark_email_sent Record that a prospect was emailed outside getcleed, so reporting and follow-ups stay correct..

Every signal quotes its source

Getcleed keeps a buying signal only if it can quote the post it came from, word for word. So when Claude tells you why someone is worth contacting, it is showing you their own words and a link to the post, not a guess.

Sending

Claude can send email and LinkedIn connection requests once you connect them in Getcleed. Those reach a real person and cannot be undone, so the server tells Claude to show you the draft and wait for your go.

Get a key

Pro $179/month (or $99/month billed annually), 7-day free trial with no charge until it ends. Trial includes the full feature set; volumes are 100 leads and 100 analyses.

For agents

/llms.txt (summary), /llms-full.txt (every tool with its arguments), /.well-known/mcp.json (descriptor).