PumpGTM MCP server

What your agent is driving

The same workspace the dashboard shows. Plays find people, sequences reach them across LinkedIn, email and X, and every reply waits for a human.

Related MCP server: SignalPipe

How it fits together

flowchart LR
  A[Your AI agent<br/>Claude, Cursor, Codex, your own] -- MCP over Streamable HTTP --> M[mcp.pumpgtm.com]
  M --> W[Your PumpGTM workspace]
  W -- find_people --> P[Buyers showing intent]
  W -- sequences --> L[LinkedIn]
  W -- sequences --> E[Email]
  W -- sequences --> X[X]
  L & E & X -- replies --> R[Human decides]
  R -- webhook reply.received --> A

Watch and read

More on the PumpGTM YouTube channel and in PumpGTM in the wild, videos founders and creators made on their own channels.

Connect

Endpoint (Streamable HTTP): https://mcp.pumpgtm.com/mcp

Two ways to authenticate, both scoped to one workspace:

• OAuth 2.1 for Claude (web and desktop) and ChatGPT. Add the endpoint as a connector and sign in. Dynamic client registration and PKCE are supported; metadata is at https://pumpgtm.com/.well-known/oauth-authorization-server. Access tokens last 30 days, refresh tokens 90.

• Workspace key for Claude Code, Cursor, Codex, the MCP SDKs, or your own agent. Sign in at app.pumpgtm.com, open MCP in the left nav, and copy the key. Send it as Authorization: Bearer eve_mcp_.. on every request. The key does not expire. Rotation is not self-serve yet: write to hello@pumpgtm.com and we rotate it for you.

The key's database row fixes the workspace. It cannot read or act on any other workspace.

import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";

const client = new Client({ name: "your-agent", version: "1.0.0" });
await client.connect(
  new StreamableHTTPClientTransport(new URL("https://mcp.pumpgtm.com/mcp"), {
    requestInit: { headers: { Authorization: "Bearer YOUR_WORKSPACE_KEY" } },
  }),
);
const { tools } = await client.listTools(); // up to 26 tools, listed below

Codex: codex mcp add pumpgtm --url https://mcp.pumpgtm.com/mcp then codex mcp login pumpgtm. Claude Code: claude mcp add --transport http pumpgtm https://mcp.pumpgtm.com/mcp --header "Authorization: Bearer eve_mcp_..".

Install as a plugin

The PumpGTM plugin bundles this server with three skills: write a cold message, find buyers, and handle replies. In Claude Code:

/plugin marketplace add pumpgtm/pumpgtm-mcp
/plugin install pumpgtm@pumpgtm

Then run /mcp and sign in to PumpGTM. The plugin's manifest, skills and server config live in github.com/pumpgtm/pumpgtm-mcp.

How results come back

• Every tool result is one MCP content block of type text whose text is a JSON string, and the same object in structuredContent. Parse the JSON.

• Most results include next: { tool, arguments, reason, requiresConfirmation, requiresNewRequestId? }. It is the suggested following call, not an instruction to skip the customer.

• Errors return isError: true and { status, retryable, changed, message, details }. changed: false means nothing was written. A missing object returns code resource_not_found.

• Tools that write take a requestId: 8 to 120 characters of letters, digits, . _ : -, starting with a letter or digit. It is an idempotency key. Use a fresh one per call; reuse one only to retry the same call.

• Metered workspaces carry Energy: one Energy is one person found. get_workspace returns energy with the monthly allowance, used and remaining, and find_people refuses with energy_exhausted when a run would exceed it. Workspaces without Energy see no such field. See Energy.

• Nothing reaches LinkedIn, email or X until a person approves it. find_people, review_people, save_sequence_draft and add_leads never send. Sending starts with set_sequence_status active on an approved sequence, and each reply is answered only through decide_reply.

A complete flow

1. get_workspace to read setup state, sequences, unfinished reviews and pending replies.

2. find_people with targeting and confirmed: false to save a Play and show the targeting summary. Then find_people with playId and confirmed: true to run it.

3. review_people with decisions and finish: true to queue the good fits into a sequence.

4. save_sequence_draft with steps, then set_sequence_status approved with expectedRevision, then active.

5. list_pending_replies, show the draft to the customer, decide_reply.

Reporting: get_workspace (view: "summary" for the funnel and account pacing, view: "activity" for the ledger) and list_leads with stage or sinceDays. The same numbers are available over REST at /docs/api.

Resources and prompts

resources/list returns six lead-search guides: gigacatalyst://lead-search/catalog, quickstart, fields, query-builder, patterns and results. Read fields before writing targeting by hand. One prompt, gigacatalyst_find_people, takes requestedCount ("10" to "100").

Versioning

Tools scheduled for removal say so in their description for at least 90 days before leaving tools/list. There is no fixed rate limit on the MCP server today; discovery is paced by each workspace's daily provider budget.

Tool reference

Generated from the live tools/list on 2026-09-23. "Read only" tools never write. Feature-gated groups return a structured error on workspaces without that feature.

Start here

get_workspace (read only)

Start here. Summary: setup state (LinkedIn, billing, finish-setup link), LinkedIn progress, Plays, eligible sequences, unfinished review, pending replies count, and (when the workspace has the email channel) its mailboxes and email campaigns. view=activity reads the append-only LinkedIn activity ledger with filters. view=x_posts lists the connected X account's recent posts with like counts and which sequence, if any, already DMs each post's likers (workspaces with the X channel).

Find and review people

find_people

Create or revise a Play from targeting and run it. Targeting may include a hiring signal (currentCompanyHiringRolesAny): the person's current company must have an open job posting for one of those roles, posted within currentCompanyHiringPostedWithinDays. Without confirmed=true it only saves the Play and returns the targeting summary for the customer to confirm. An unresolved required company is preserved in the saved draft and returned under companyResolution; the Play cannot run until the customer corrects or explicitly removes it in a revision. With confirmed=true, a ready Play runs discovery and returns candidates in retrieval order. Pass playId alone to rerun an existing ready Play. Optional sequenceId sets the Play's default sequence. Creates no leads and contacts no one.

review_people

Without decisions: read one review batch with its candidates and saved choices. With decisions: record the customer's explicit good_fit and not_a_fit choices; a top-level sequenceId applies to every good fit, finish=true completes the review and queues good fits into the sequence. For add all, mark every candidate good_fit with finish=true. Sends nothing in this call.

search_known_people (read only)

Search a company, professional role, or explicitly stated accelerator cohort in permitted shared professional evidence. Returns at most 20 matching identities; coverage is incomplete and includes labelled historical roles and interpretations. This is not a live provider search, does not expose other customers' lists or messages, and does not authorize outreach. Check source dates before recommending someone.

get_lead_profile (read only)

Read source-dated public identities, available employment history, public activity and relationship observations for a lead owned by this workspace. Public profile links and AI interpretations require review. This does not fetch providers, change identities, enroll or contact anyone.

Sequences

list_sequences (read only)

Sequences with steps, approval state, status, and exact enrolled-lead counts. Pass sequenceId to read one sequence with its exact revision before editing.

save_sequence_draft

Without sequenceId: create a complete new sequence (name plus ordered steps). With sequenceId and expectedRevision: replace a draft's complete step list; move active or paused sequences to draft first. Steps are connect, message, engage (LinkedIn), email (subject plus body; only when the workspace has email enabled), or x_dm (an X direct message to a post liker; an X sequence is x_dm steps only, for workspaces with the X channel). When any LinkedIn step is present step 0 must be connect; an email-only sequence needs no connect. delayDays counts from the previous step (the step after connect waits for the invite to be accepted) and later steps are skipped once the person replies on any channel. {{firstName}} {{fullName}} {{company}} {{title}} render on both channels. Example mixed flow: connect, message +1d, email +2d, email +2d, email +3d. The result stays a stopped draft that needs approval, then activation, through set_sequence_status.

set_sequence_status

For a LinkedIn sequence (sequenceId): status=approved records the customer's approval of one exact draft revision (expectedRevision required) and keeps it stopped; active starts outreach for an approved sequence, paused stops it for every enrolled lead, draft reopens it for editing. For an email campaign (emailCampaignId): active launches sending inside its schedule and limits, paused stops it, draft reopens it; approved does not apply. Each is a separate explicit customer decision.

Leads

list_leads (read only)

This workspace's leads with LinkedIn and sequence progress. stage is cumulative (reached this milestone or beyond); stageExact is the current position only. Count is exact even when the page is limited. Pass leadId to read one lead in full.

add_leads

Queue leads into one approved active sequence: 1 to 500 manual LinkedIn profiles, CSV content, or a saved Sales Navigator list URL. Manual and CSV finish immediately and return added, duplicate, and invalid counts plus stable addedLeadIds. Sales Navigator runs in the background and auto-enrolls; use method=import_status with its batchId to check. Nothing is sent in this call.

The input is one of these shapes:

• method: "manual" with requestId (required), sequenceId (required), leads (required)

• method: "csv" with requestId (required), sequenceId (required), csvContent (required)

• method: "sales_navigator" with requestId (required), sequenceId (required), accountId, listUrl (required)

• method: "import_status" with batchId (required)

remove_leads

Only when the customer explicitly asks to undo an add or stop leads. Target lead IDs or one batchId from add_leads. Uncontacted leads leave the queue; contacted leads keep history and get no further automated steps. Sent invitations and messages cannot be reversed.

The input is one of these shapes:

• target: "leads" with leadIds (required)

• target: "import" with batchId (required)

Replies

list_pending_replies (read only)

Inbound LinkedIn replies frozen for human review, each with PumpGTM's draft answer. Read-only.

decide_reply

Apply one explicit human decision to a pending reply. send, invite, and booking_link contact the prospect; opt_out is permanent. Show the draft and ask the customer first.

Cold messages

get_cold_message_examples (read only)

A random sample from PumpGTM's library of the most-liked public posts on X about writing cold emails and DMs, each with its link and why it was kept. Use them as references when drafting or critiquing a cold message; credit the author and do not copy them word for word.

Post engagers and X (X tools need the X channel)

reach_post_engagers

LinkedIn post URL plus message: PumpGTM creates a Play with its own approved sequence (note-less connection request, then your message), fetches every reactor and commenter in the background (up to 500), and enrolls all of them; call again with only playId for progress. X post URL (x.com/…/status/…) plus message, or plus an existing X sequenceId: its likers and repliers are collected into Lead Universe for review as they engage, from now on; the customer adds the ones they want to that X sequence there (or with add_to_sequence). followers=true instead of a post URL does the same for the account's new followers (workspaces with the X channel; call again with only watchId for people waiting for review, DMs sent, replies). Nothing is enrolled or sent in this call.

x_account

One action from a connected X account: follow a person (target is an X profile URL or @handle), or like or repost one post (target is an X post URL). as picks which connected account acts when the workspace has several (get_workspace view=x_posts lists them); default is the first connected. Needs the X channel. It never sends a DM or writes a new post.

Account universe (needs the account universe feature)

research_competitor

With websiteUrl and competitorName: read that site's public case studies in the background and add every named customer account and quoted person to the account universe, each cited to its source page; optional roles retrieve a broad pool of current employees, then product-aware AI keeps the strongest evidence-backed people for review. Supply productBrief when the Play promotes a different product or the workspace has no confirmed profile. Without websiteUrl and competitorName: list the sourced account universe (optional playId narrows to one competitor and reports research status). Review material only; enrolls and contacts no one.

reach_universe

Pick people from the account universe (by competitor name, playId, or exact candidateIds; notYetEnrolled skips anyone already in LinkedIn outreach) and reach them on one channel. channel=email puts everyone with a known email into one of the workspace's own email campaigns, either campaignId or a new draft named campaignName, and may set the campaign's steps (plain text, {{firstName}} {{company}} {{title}} placeholders, delayDays between steps), schedule, sending mailboxIds (or allMailboxes), and dailyLimit in the same call; people without an email are skipped, and findEmails=true first looks up missing addresses, up to maxEmailLookups and a daily limit. channel=linkedin enrolls them into an active approved sequence by sequenceId through the ordinary paced engine. Nothing is launched or sent in this call.

add_to_sequence

Pick people from the account universe (by competitor name, playId, or exact candidateIds; notYetEnrolled skips anyone already in a sequence) and add them to one sequence: an existing non-archived sequenceId from list_sequences, or a new draft named name built from template linkedin / email / linkedin_email (then edit its steps with save_sequence_draft). Email-only sequences skip people without a known email; mixed sequences keep them and their email steps wait until an address is known; findEmails=true first looks up missing addresses, metered. Adding never approves, launches, or sends: the customer approves and starts the sequence with set_sequence_status.

CRM (needs the CRM feature)

get_pipeline (read only)

Read your workspace's CRM opportunities and company lifecycle. Money is in minor units and totals are separated by currency. Probabilities are explicit stage/team estimates, not calibrated predictions or verified revenue. Requires the CRM feature.

get_company (read only)

Company, linked lead contacts, opportunities, success plan, and latest 100 source-attributed events. Recorded/imported signals do not imply a live provider connection.

save_company

Create or revise a CRM company and its customer success plan. Use a new UUID and expected_revision=0 to create; use the current revision to edit. Lifecycle is your team's assessment; active never means Stripe-verified. Do not invent customer status. Does not send, enroll, or bill anyone.

save_opportunity

Create or revise a deal for an existing CRM company. Ask for missing value/currency; null value means unknown. Use a new UUID/revision=0 to create, otherwise current revision. Stage does not change outreach or company lifecycle. Won means recorded won, not paid. Only set probability_override when the user supplies an estimate.

add_company_contact

Add a company contact, optionally linked to an existing PumpGTM lead in this workspace. Never guess a lead match from a company name. Does not create or enroll outreach leads.

record_customer_signal

Append a dated note, meeting, reply, product engagement, risk, or milestone, with its source link. Use evidence, not assumptions. Source names are attribution, not provider verification. Does not read a provider or send to Slack. A note never refreshes contact recency.

Not on this server yet

• Managing several client workspaces from one connection. Today one key is one workspace. The agency layer is in progress; write to hello@pumpgtm.com.

• Webhooks are managed over REST, not MCP: POST /api/v1/webhooks with the same key, see /docs/api.

Questions: hello@pumpgtm.com.

Guides and reading