Run LeadMagnet from your AI assistant
The LeadMagnet MCP server lets Claude (and other MCP clients) read your leads, launch campaigns, and — inside your pacing limits — reach out, all through conversation. Connecting takes one URL and a sign-in. There is no token to paste and no config file to edit.
Sign-in is handled by OAuth when you connect — you approve access in your browser, the same account you use for the dashboard. Nothing else to configure.
Opens Claude with the connector pre-filled. You'll still sign in and approve access.
- Open Settings → Connectors in Claude.
- Click Add custom connector.
- Paste the server URL: https://leadmagnetinc.com/api/mcp
- Click through the sign-in prompt that opens in your browser and approve access.
- The 10 LeadMagnet tools are now available. Try: “Show me my LeadMagnet dashboard.”
- Open ChatGPT Settings → Connectors (or chatgpt.com/#settings/Connectors).
- Enable Developer Mode if prompted — it's under Advanced.
- Click Create. A New App modal opens.
- Name: LeadMagnet
- MCP Server URL: https://leadmagnetinc.com/api/mcp
- Authentication: OAuth
- Check “I understand and want to continue” on the risk warning.
- Click Create.
- ChatGPT prompts for authorization the first time a tool is called.
get_dashboardAccount overview: lead counts, emails logged, active campaigns, recent activity.
get_subscriptionCurrent plan and trial/subscription status.
list_leadsCaptured and AI-scored leads for the account.
recommend_leadsAI-recommended leads worth prioritizing, based on your ICP and signals.
list_clientsAgency client workspaces (Agency/Scale plans).
list_sequencesYour Gmail follow-up email sequences.
create_campaignStart a LinkedIn lead-capture campaign from a post URL.
create_sequenceCreate a Gmail follow-up email sequence (Pro+).
send_connectionpacedSend a LinkedIn connection request to a profile.
send_dmpacedSend a LinkedIn message to a profile.
Talk to your assistant naturally — it picks the tool.
send_connection and send_dmrun through LeadMagnet's pacing engine. The agent cannot bypass it — if a check fails, the tool returns a governed rejection and nothing is sent.
| Control | Effect |
|---|---|
| Daily / weekly caps | Sends over your limit are refused. |
| Quiet hours | No outbound activity during your configured quiet window. |
| Warm-up ramp | New accounts start with low caps that rise over ~3 weeks. |
| Kill switch | One switch halts all sending immediately. |
Advanced: local server (stdio)
The one-click OAuth flow above is the recommended path. If you'd rather run the server locally over stdio — for development, or with a client that doesn't support remote MCP — the mcp-server/ folder in the GitHub repo still works.
- Run npm install inside mcp-server/.
- Copy your Supabase access token (dev tools → Application → Local Storage → the sb-...-auth-token value). This token grants full account access — treat it like a password, and note it expires periodically.
- Add the server to your client config with that token:
{
"mcpServers": {
"leadmagnet": {
"command": "node",
"args": ["/absolute/path/to/mcp-server/index.js"],
"env": {
"LEADMAGNET_BASE_URL": "https://leadmagnetinc.com",
"LEADMAGNET_TOKEN": "YOUR_ACCESS_TOKEN"
}
}
}
}