Linkedin Buying Signals

com.getcleedPublished by getcleed.comOfficial publisherv1.1.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

A remote MCP server for Getcleed that lets an assistant find B2B prospects showing buying signals on LinkedIn, inspect their signals, and draft or send outreach

What you can do
Inspect the account setup: active ICP, signal definitions, pipeline statistics, and a fictional sample pipeline that works without credentials. Search and read saved prospects, including each detected signal with its verbatim quote and source link. Source new leads from LinkedIn posts matching the account's signals, or save LinkedIn profiles by URL, then import candidates against the import quota. Run the signal pipeline on prospects to enrich company data and detect buying signals. Draft personalised emails and LinkedIn connection notes in the prospect's language, and send them from connected accounts. Record outreach done outside the tool and create new custom buying signals in plain语言.
When to use it
Useful for B2B sales or recruiting teams already on Getcleed who want an assistant to surface LinkedIn prospects with buying signals, review why each was flagged, and prepare or send outreach without leaving the conversation.
Requirements
A remote streamable HTTP endpoint at the provider's site; no package or local runtime. An account is needed for most tools, though the sample pipeline works without credentials. Sending requires a mailbox and a LinkedIn account connected under Integrations. Quotas apply to imports, monthly analysis and the plan.
Before you install
send_email and send_linkedin_message reach real people immediately and cannot be undone; drafts are saved but not sent until you ask. Importing and analysis consume plan quota. The server reads LinkedIn activity and prospect data and sends outreach through connected accounts, so review drafts and recipients before sending.

Installation

In SourceWeft

  1. Open Linkedin Buying Signals in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.getcleed%2Flinkedin-buying-signals/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "linkedin-buying-signals": {
      "type": "http",
      "url": "https://www.getcleed.com/api/mcp"
    }
  }
}

README

This repository has no README.

Tools

16

get_sample_pipeline

Sample pipeline (no account needed)

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. Nothing in it is a real person.

Takes no parameters.

list_prospects

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.

ParameterslimittitleoffsetsearchcompanycountryhasEmailindustryminSignalssignalTypenotContactedenrichmentStatus

get_prospect

Get one 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.

ParametersprospectIdlinkedinUrl

get_pipeline_stats

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.

Takes no parameters.

list_signals

List signal definitions

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.

ParametersenabledOnly

get_icp

Get the ideal customer profile

The active ICP: target roles, industries, countries, company sizes, relevant keywords and any exclusions. This is what sourcing and scoring filter against.

Takes no parameters.

add_leads_from_urls

Add leads from LinkedIn URLs

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

ParameterslistIdlinkedinUrlsrequired

find_leads_from_signals

Find new leads from signal topics

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.

ParameterssignalTypepostsPerSignal

import_sourced_leads

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.

ParameterslistIdtokensrequiredsignalTyperequired

analyze_prospects

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.

ParameterslimitprospectIds

draft_email

Draft an 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.

ParameterslanguageprospectIdregeneratelinkedinUrlsignalIndex

draft_linkedin_message

Draft a 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 send_linkedin_message.

ParameterslanguageprospectIdregeneratelinkedinUrl

send_email

Send an 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.

ParametersbodysubjectprospectIdlinkedinUrl

send_linkedin_message

Send a LinkedIn connection request

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.

ParametersmessageprospectIdlinkedinUrl

mark_email_sent

Mark as contacted

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

ParametersprospectIdlinkedinUrl

create_custom_signal

Create a 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.

ParametersnamerequireddetectsrequiredexampleTitleexampleDetail

Version history

1
  1. v1.1.0LatestSep 25, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.