Official MCP server for Leadpipe intent and data APIs.
Use this server to give agents direct access to:
- topic discovery
- website topic analysis
- audience preview and ad hoc query
- saved audience management
- audience status, results, runs, stats, and exports
- visitor data lookup
- tracking pixel management
- account health and credit status
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/mcpYou will need:
export LEADPIPE_API_KEY=sk_...Optional advanced override:
export LEADPIPE_BASE_URL=https://api.aws53.cloudLEADPIPE_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/mcpThen confirm it is configured:
codex mcp listIf you just want to verify the package runs:
npx -y @leadpipe/mcpFor local development or repo hacking:
npm install
npm run build
node dist/index.jsFor iterative local development:
npm run devLocal 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_topics
get_audience_filterspreview_audiencequery_audiencelist_audiencesget_audiencecreate_audienceupdate_audiencedelete_audience
get_audience_statusget_audience_resultslist_audience_runsget_audience_statsexport_audience
query_visitor_data
list_pixelscreate_pixelupdate_pixel
get_account_status
discover-audience-topicsoperate-saved-audienceinvestigate-visitor-data
See examples/prompt-examples.md for copy-paste prompts that work well with this MCP server.
Good starting prompts:
- "Find 5-10 B2B topics for cloud cost optimization software, compare their recent trends, and preview an audience."
- "Create a saved audience for these topics, activate it, wait until it is ready, and then summarize the first page of results."
- "Check the status of audience
<audience-id>. If it is ready, export it and give me the download URL." - "Investigate visitor activity for
example.comover the last 30 days and tell me whether our tracking setup looks healthy." - "List our pixels, find any paused ones, and explain what needs attention."
For more structured operational flows, see:
leadpipe://docs/authleadpipe://docs/workflowsleadpipe://docs/data-api
- Search or analyze topics
- Preview audience size
- Create or update a saved audience
- Check status until the audience is ready
- Fetch results or export CSV
- Check
get_account_status - Query visitor activity with
query_visitor_data - Inspect or create pixels with
list_pixels/create_pixel - Pause or reactivate tracking with
update_pixel
npm run typecheck
npm run buildMIT