Manage Facebook and Instagram lead ad delivery: CRMs, alerts, autoresponders and test leads.
Connect Runs on your machine
claude mcp add mcp -e LEADSYNC_API_KEY=<LEADSYNC_API_KEY> -- npx -y @leadsync/[email protected]{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@leadsync/[email protected]"
],
"env": {
"LEADSYNC_API_KEY": "<LEADSYNC_API_KEY>"
}
}
}
}{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@leadsync/[email protected]"
],
"env": {
"LEADSYNC_API_KEY": "<LEADSYNC_API_KEY>"
}
}
}
}{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@leadsync/[email protected]"
],
"env": {
"LEADSYNC_API_KEY": "<LEADSYNC_API_KEY>"
}
}
}
}Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
LEADSYNC_API_KEYOptional, secret | LeadSync API key (Account, Settings, API keys). Optional if you ran npx @leadsync/skills login, which saves it to ~/.leadsync/.env. |
Details
| Package | @leadsync/[email protected] (NPM, stdio) |
| First published | 29 Oct 2026 |
| Last updated | 29 Oct 2026 |
| Registry name | me.leadsync/mcp |
More marketing and seo servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.