pumpgtm-mcp

<p align="center"><a href="https://pumpgtm.com"><img src="assets/banner.png" alt="PumpGTM" width="100%"></a></p> <h1 align="center">PumpGTM MCP server</h1> <p align="center"><b>Run LinkedIn, email and X outreach from any AI agent.</b><br> PumpGTM finds the buyers showing intent this week, drafts and sends the outreach from your own accounts inside each platform's limits, and hands every reply back to a human. This is the public reference for the hosted MCP server at <code>https://mcp.pumpgtm.com/mcp</code>.</p> <p align="center"> <a href="https://pumpgtm.com/docs/mcp"><img alt="Docs" src="https://img.shields.io/badge/docs-pumpgtm.com%2Fdocs%2Fmcp-2f5cff"></a> <a href="https://modelcontextprotocol.io"><img alt="MCP" src="https://img.shields.io/badge/MCP-Streamable%20HTTP%20%2B%20OAuth%202.1-000000"></a> <a href="tools.json"><img alt="Tools" src="https://img.shields.io/badge/tools-34-1f883d"></a> <a href="https://github.com/pumpgtm/pumpgtm-api"><img alt="REST API" src="https://img.shields.io/badge/REST%20API-OpenAPI%203.1-6f42c1"></a> <a href="https://pumpgtm.com/yc"><img alt="Backed by Y Combinator" src="https://img.shields.io/badge/Backed%20by-Y%20Combinator-F26522"></a> <a href="https://pumpgtm.com/blog/ai-founder-led-outbound-system"><img alt="Runs outbound for 10+ YC companies" src="https://img.shields.io/badge/runs%20outbound%20for-10%2B%20YC%20companies-F26522"></a> <a href="LICENSE"><img alt="License" src="https://img.shields.io/badge/license-MIT-lightgrey"></a> </p> <p align="center"> <a href="https://pumpgtm.com/docs/quickstart">Quickstart</a> · <a href="https://pumpgtm.com/docs/mcp">Docs</a> · <a href="tools.json">tools.json</a> · <a href="https://github.com/pumpgtm/pumpgtm-api">REST API</a> · <a href="https://pumpgtm.com/mcp/platforms">Platforms and agencies</a> · <a href="https://www.youtube.com/@pumpgtm">YouTube</a> </p>

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.

<p align="center"><img src="assets/plays.png" alt="PumpGTM Plays: describe who you want, start from a list, or reach everyone who engaged with a post" width="100%"></p> <p align="center"><img src="assets/sequences.png" alt="A running PumpGTM sequence with its funnel and message variants" width="100%"></p>

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

<table> <tr> <td width="50%" align="center"><a href="https://pumpgtm.com/blog/what-is-pumpgtm-how-it-works"><img src="https://img.youtube.com/vi/wEb9ZDUIsc0/hqdefault.jpg" alt="What is PumpGTM and how does it work" width="100%"></a><br>_{<b>What is PumpGTM, and how does it actually work?</b><br>4 minute walkthrough}</td> <td width="50%" align="center"><a href="https://x.com/NamanyayG/article/2097783972302557668"><img src="https://pumpgtm.com/blog/covers/ai-founder-led-outbound-system.png" alt="Using AI to run founder-led outbound for 10 YC companies" width="100%"></a><br>_{<b>Using AI to run founder-led outbound for 10 YC companies</b><br>Namanyay's article on X: one lead universe, shared prospects, copy measured by meetings. <a href="https://pumpgtm.com/blog/ai-founder-led-outbound-system">Read on pumpgtm.com</a>}</td> </tr> </table>

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), Claude Code, Codex, Cursor, ChatGPT and Grok. Add the endpoint and sign in; no key is needed. 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 your own agent, the MCP SDKs, and the REST API. 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 34 tools, depending on the workspace's features

ChatGPT (until the PumpGTM listing is approved in the ChatGPT directory; Developer mode is no longer needed): open Plugins (chatgpt.com/plugins), click + and choose Add custom MCP server. Name it PumpGTM, paste https://mcp.pumpgtm.com/mcp as the Server URL, keep OAuth, click I understand and want to continue, then Create as a plugin. Open your personal plugins (chatgpt.com/plugins?view=personal), open PumpGTM and click + to install it, then sign in to PumpGTM and allow the connection. In a chat, type @PumpGTM and ask it to find buyers.

Claude Code: claude mcp add --transport http pumpgtm https://mcp.pumpgtm.com/mcp, then run /mcp (or claude mcp login pumpgtm) and sign in. Codex: codex mcp add pumpgtm --url https://mcp.pumpgtm.com/mcp then codex mcp login pumpgtm. Cursor: add a server with only the URL and sign in when it asks. Cline: add "pumpgtm": { "type": "streamableHttp", "url": "https://mcp.pumpgtm.com/mcp" } under mcpServers in cline_mcp_settings.json and sign in when it asks. Grok: at grok.com/connectors choose New Connector, then Custom, paste https://mcp.pumpgtm.com/mcp, and sign in (works on the free plan).

Install as a plugin

The PumpGTM plugin bundles this server with five skills: write a cold message, make a message sound human, find buyers, handle replies, and look up a person. 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.

In Codex:

codex plugin marketplace add pumpgtm/pumpgtm-mcp
codex plugin add pumpgtm@pumpgtm
codex mcp login pumpgtm

In Gemini CLI:

gemini extensions install https://github.com/pumpgtm/pumpgtm-mcp

Then run /mcp auth pumpgtm and sign in.

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.

Tool permissions

Every tool is classified for AI clients that ask before acting. Read tools never change anything. Write tools change workspace records but contact no one. Sensitive writes contact a third party, act in public, or spend money, so an AI client should show the details and get the user's yes each time. Hints in tools/list match this table (readOnlyHint, destructiveHint, openWorldHint).

| Tool | Class | Side effect | |---|---|---| | get_cold_message_examples | Read | none | | get_company | Read | none | | get_lead_profile | Read | none | | get_pipeline | Read | none | | get_workspace | Read | none | | get_x_play_review | Read | none | | list_leads | Read | none | | list_pending_replies | Read | none | | list_sequences | Read | none | | list_signal_events | Read | none | | list_signal_types | Read | none | | search_known_people | Read | none | | add_company_contact | Write | changes workspace records only; contacts no one | | record_customer_signal | Write | changes workspace records only; contacts no one | | remove_leads | Write | stops future automation for those people; never deletes history | | save_company | Write | changes workspace records only; contacts no one | | save_opportunity | Write | changes workspace records only; contacts no one | | add_leads | Sensitive write | people enter a sequence and a live sequence will contact them | | add_to_sequence | Sensitive write | people enter a sequence and a live sequence will contact them | | decide_reply | Sensitive write | send, invite and booking_link message the prospect at once; opt_out is permanent | | energy | Sensitive write | reading changes nothing; turning on automatic top-up authorizes future card charges | | enrich_person | Sensitive write | spends workspace Energy (paid) | | find_people | Sensitive write | with confirmed=true runs a paid search (can use Energy); never contacts anyone | | manage_x_play | Sensitive write | resuming or enabling enrollment can start future X outreach | | reach_post_engagers | Sensitive write | LinkedIn: enrolls the post's engagers into a live sequence; X: collects them for review | | reach_universe | Sensitive write | people enter a sequence or email campaign that can contact them | | research_competitor | Sensitive write | starts paid background research; never contacts anyone | | review_people | Sensitive write | good fits enter the chosen sequence; a live sequence will contact them | | review_x_play_candidates | Sensitive write | good fits enter the Play's X sequence; an active sequence will DM them | | save_sequence_draft | Sensitive write | the saved sequence is live and its steps contact the people enrolled in it | | sequence_email_settings | Write | changes which mailboxes, schedule and daily limit a sequence uses; sends nothing | | set_lead_input | Sensitive write | releases a held message step for that person | | set_sequence_status | Sensitive write | active or approved lets the paced engine contact enrolled people | | x_account | Sensitive write | follows, likes or reposts publicly from the connected X account |

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