Connects Claude to Leadpipe's intent and data APIs for B2B audience building and visitor analytics. You get tools for topic discovery, audience preview and management, visitor data queries, tracking pixel control, and export workflows. Authentication is API key based. The typical flow is search topics, preview size, create or update a saved audience, poll status, then fetch results or CSV. Also covers account health checks and pixel diagnostics. Useful if you're running Leadpipe for intent data and want agents to handle audience research, activation monitoring, or visitor activity investigation without jumping between the API docs and your terminal.
Official MCP server for Leadpipe intent and data APIs.
Use this server to give agents direct access to:
Leadpipe MCP wraps the public Leadpipe intent and data APIs in a local MCP server that agents can use over stdio.
This server is API-key authenticated by default so the full audience workflow, visitor data access, and pixel management workflows are available to agents.
Most users do not need to clone this repo or build from source. The published package is:
npx -y @leadpipe/mcp
You will need:
export LEADPIPE_API_KEY=sk_...
Optional advanced override:
export LEADPIPE_BASE_URL=https://api.aws53.cloud
LEADPIPE_BASE_URL only needs to change if you are pointing at a non-default environment.
Add this to your Claude Desktop MCP config:
{
"mcpServers": {
"leadpipe": {
"command": "npx",
"args": ["-y", "@leadpipe/mcp"],
"env": {
"LEADPIPE_API_KEY": "sk_..."
}
}
}
}
Add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"leadpipe": {
"command": "npx",
"args": ["-y", "@leadpipe/mcp"],
"env": {
"LEADPIPE_API_KEY": "sk_..."
}
}
}
}
Add the server with the Codex CLI:
codex mcp add leadpipe --env LEADPIPE_API_KEY=sk_... -- npx -y @leadpipe/mcp
Then confirm it is configured:
codex mcp list
If you just want to verify the package runs:
npx -y @leadpipe/mcp
For local development or repo hacking:
npm install
npm run build
node dist/index.js
For iterative local development:
npm run dev
Local source build MCP config:
{
"mcpServers": {
"leadpipe": {
"command": "node",
"args": ["/absolute/path/to/mcp/dist/index.js"],
"env": {
"LEADPIPE_API_KEY": "sk_..."
}
}
}
}
list_topicsget_topic_facetssearch_topicsget_topic_trendcompare_topicsget_topic_moversanalyze_website_topicsget_audience_filterspreview_audiencequery_audiencelist_audiencesget_audiencecreate_audienceupdate_audiencedelete_audienceget_audience_statusget_audience_resultslist_audience_runsget_audience_statsexport_audiencequery_visitor_datalist_pixelscreate_pixelupdate_pixelget_account_statusdiscover-audience-topicsoperate-saved-audienceinvestigate-visitor-dataSee examples/prompt-examples.md for copy-paste prompts that work well with this MCP server.
Good starting prompts:
<audience-id>. If it is ready, export it and give me the download URL."example.com over the last 30 days and tell me whether our tracking setup looks healthy."For more structured operational flows, see:
leadpipe://docs/authleadpipe://docs/workflowsleadpipe://docs/data-apiget_account_statusquery_visitor_datalist_pixels / create_pixelupdate_pixelnpm run typecheck
npm run build
MIT
LEADPIPE_API_KEY*secretLeadpipe API key used for authenticated intent and data workflows.
LEADPIPE_BASE_URLOptional alternate Leadpipe API base URL for non-default environments.
com.mcparmory/google-sheets
domdomegg/google-sheets-mcp
henilcalagiya/google-sheets-mcp
cct15/war-dashboard-data
moooonad/mcp-google-sheets-full
io.github.br0ski777/csv-to-json