Model Context Protocol (MCP) server for Apollo.io API integration
LinkedIn Buying Signals is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Find B2B prospects showing buying signals on LinkedIn and draft the outreach.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http linkedin-buying-signals-mcp https://www.getcleed.com/api/mcp
# 2 — ask your agent for something these tools do
# list_prospects, get_prospect, get_pipeline_stats and 12 more
LinkedIn Buying Signals costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http linkedin-buying-signals-mcp https://www.getcleed.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
15 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| search | string | no | Free text matched against first name, last name, company and title |
| company | string | no | — |
| industry | string | no | — |
| title | string | no | Job title contains this text |
| country | string | no | — |
| signalType | string | no | Only prospects carrying a signal of this type (see list_signals) |
| minSignals | integer | no | Only prospects with at least this many signals |
| hasEmail | boolean | no | — |
| enrichmentStatus | string | no | — |
| notContacted | boolean | no | Only prospects with no email sent yet |
| limit | integer | no | How many to return (max 50) |
| offset | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| prospectId | string | no | The prospect id from list_prospects |
| linkedinUrl | string | no | Their LinkedIn profile URL, if the id is unknown |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| enabledOnly | boolean | no | — |
The active ICP: target roles, industries, countries, company sizes, relevant keywords and any exclusions. This is what sourcing and scoring filter against.
No parameter schema on file.
Save LinkedIn profiles as prospects and enrich them (name, role, company, industry, location, language). Skips anyone already saved. Counts against the import quota.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| linkedinUrls | array | yes | LinkedIn profile URLs |
| listId | string | no | Optional list to add them to (see get_icp for list ids) |
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: pass the returned candidates to import_sourced_leads. Spends a little of the monthly sourcing budget.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| signalType | string | no | Which signal to source for; omit to use the first enabled one (see list_signals) |
| postsPerSignal | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| signalType | string | yes | The signalType returned by find_leads_from_signals |
| tokens | array | yes | The token values of the candidates to import |
| listId | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| prospectIds | array | no | Which prospects to analyze; omit to take those with no signals yet |
| limit | integer | no | Cap when prospectIds is omitted |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| prospectId | string | no | — |
| linkedinUrl | string | no | — |
| signalIndex | integer | no | Which signal to lead with |
| regenerate | boolean | no | Ignore any cached draft |
| language | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| prospectId | string | no | — |
| linkedinUrl | string | no | — |
| regenerate | boolean | no | — |
| language | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| prospectId | string | no | — |
| linkedinUrl | string | no | — |
| subject | string | no | Omit to use the saved draft |
| body | string | no | Omit to use the saved draft |
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 Integrations.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| prospectId | string | no | — |
| linkedinUrl | string | no | — |
| message | string | no | The note, max 300 characters. Omit to use the saved draft |
Record that a prospect was emailed outside getcleed, so reporting and follow-ups stay correct.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| prospectId | string | no | — |
| linkedinUrl | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Short display name |
| detects | string | yes | What to look for, in plain language |
| exampleTitle | string | no | — |
| exampleDetail | string | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install LinkedIn Buying Signals or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish LinkedIn Buying Signals can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.