The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Leadpipe listing page.
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:
You will need:
Optional advanced override:
LEADPIPE_BASE_URL only needs to change if you are pointing at a non-default environment.
Add this to your Claude Desktop MCP config:
Add this to ~/.cursor/mcp.json:
Add the server with the Codex CLI:
Then confirm it is configured:
If you just want to verify the package runs:
For local development or repo hacking:
For iterative local development:
Local source build MCP config:
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_pixelMIT