PumpGTM MCP server

What PumpGTM MCP server MCP server does

PumpGTM MCP server MCP server gives AI clients access to a PumpGTM workspace for buyer discovery, lead management, and outbound workflows. The hosted service is available at https://mcp.pumpgtm.com/mcp and uses MCP over Streamable HTTP.

An agent can inspect workspace information, search for people showing intent, review discovered people, save or activate sequence drafts, add and list leads, retrieve cold-message examples, and reach people who engaged with posts. The supported outreach channels described by the project are LinkedIn, email, and X. Replies are returned for human handling rather than being left entirely to the agent.

How it works

The agent connects to the hosted endpoint and operates within one authenticated PumpGTM workspace. OAuth 2.1 is available for supported clients, with dynamic client registration and PKCE. OAuth access tokens last 30 days and refresh tokens last 90 days. A workspace key is also available for custom agents, MCP SDK clients, and the REST API; it is sent as a bearer token and is tied to a single workspace.

Discovery and preparation do not contact prospects. find_people, review_people, save_sequence_draft, and add_leads can prepare records and sequences without sending messages. Outreach begins when an approved sequence is activated with set_sequence_status. Reply handling uses decide_reply, according to the project’s workflow description.

Tool responses contain a text content block whose value is a JSON string, along with the same object in structured content. Write operations accept a requestId for idempotency. Clients should use a new identifier for each new write and reuse one only when retrying the same call.

Setup and configuration

For clients that support the hosted OAuth flow, add the endpoint and complete the PumpGTM sign-in process. Claude Code can be configured with claude mcp add --transport http pumpgtm https://mcp.pumpgtm.com/mcp, followed by claude mcp login pumpgtm. Codex uses codex mcp add pumpgtm --url https://mcp.pumpgtm.com/mcp and codex mcp login pumpgtm. Cursor and Cline can use the same URL and then authenticate when prompted.

Custom agents can connect with the MCP SDK and provide Authorization: Bearer YOUR_WORKSPACE_KEY. The key is created in the PumpGTM application under the MCP section. No environment variable is required by the hosted service, because authentication is performed through OAuth or a request header.

Tools and capabilities

Key tools documented for PumpGTM MCP server MCP server include:

• get_workspace for workspace information and, where applicable, Energy usage.
• find_people and review_people for discovering and evaluating potential buyers.
• add_leads and list_leads for managing lead records.
• save_sequence_draft and set_sequence_status for preparing and activating outreach sequences.
• get_cold_message_examples for retrieving message examples.
• reach_post_engagers for reaching people who engaged with a post.

Limitations and notes

PumpGTM is a paid SaaS product with plans starting at $75 per month. The service operates on behalf of the authenticated workspace and cannot use a workspace key to access another workspace. A workspace’s Energy allowance can limit find_people; the tool can refuse a run when the requested work would exceed the remaining allowance.

The project states that sending requires approval: prepared records and drafts do not contact people, and activating an approved sequence starts sending. Sensitive actions should therefore be shown to the user for confirmation by clients that support MCP permission hints. Workspace-key rotation is not self-service; the documentation says to contact PumpGTM support for rotation.