People data MCP
Connect your MCP client to PumpGTM and call enrich_person to turn an email or LinkedIn URL into a profile, X account and work email.
Updated · View as Markdown
Use the same people-data operation as the REST API from your connected agent. The tool returns structured person data and per-call Energy usage.
Connect your agent
Add this remote MCP server in your client and sign in to your PumpGTM workspace:
https://mcp.pumpgtm.com/mcpUse your client's remote HTTP and OAuth connection flow. The MCP setup guide covers supported clients. For a custom bearer-token client, copy the existing configuration from your workspace's MCP page. Keep the key out of prompts, source control, and public browser code.
Your workspace needs Energy enabled and available. Check billing before paid work. People-data calls use the same balance as the REST API.
Call enrich_person
Ask your agent:
Find the X account for arthur@example.com with PumpGTM. Show the Energy used. Do not start outreach.
The agent calls the following tool with these arguments:
{
"name": "enrich_person",
"arguments": { "email": "arthur@example.com", "find": ["x"] }
}Send exactly one of email or linkedin (a public LinkedIn person URL). find is optional: "x" adds their X account, returned only with public evidence that it is theirs, and "work_email" adds a work email. The result is { id, person, missing, energyUsed }. See the full response example, or switch to MCP in the interactive person reveal.
Use the returned context
person holds name, title, headline, location, company, LinkedIn URL, and the X account and work email when asked for and found. It is null when nobody matches. Missing facts are null. Check workEmail.matchesCompanyDomain before using an email.
person.connections appears only when we have previously observed public follow relationships for the person, with source URLs and observation times. We do not claim a complete network for every person.
Your agent can combine this with our YC founder dataset and investor dataset: choose a person, enrich them, and bring the result into your own workflow.
Paid calls need deliberate retries
One Energy is $0.05. The same people-data pricing and error rules apply over API and MCP. The tool can consume Energy, so it is not marked read-only or idempotent. Repeated calls may be billed again. Never automatically retry a timeout or unknown failure.
When something you asked for in find does not come back, missing says why, and the rest of the profile is still returned. energyUsed reports the Energy the call spent.
This tool does not save a lead, create a sequence, send a message, or connect a social account. Use find_people for audience discovery and the existing outreach tools only when you intend to start an outreach workflow.