Official MCP server for Leadpipe intent and data APIs.
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
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @leadpipe/mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-leadpipe-com-leadpipe": {
"command": "npx",
"args": [
"-y",
"@leadpipe/mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@leadpipe/mcpnpmio.github.leadpipe-com/leadpipe works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.