MCP & API
Your lead feed, inside Claude, ChatGPT and your own tools
Tradeping has a remote MCP server and a REST API. Ask your assistant for today's roofing leads in Nashville, have it tighten a draft, then send it from your mailbox — with the same plan limits, verified-only leads and send caps as the web app.
Connect the MCP server
Server URL: https://gettradeping.com/mcp (Streamable HTTP). Sign in with your Tradeping account when your app asks; no key to copy.
- Claude (claude.ai or desktop): Settings → Connectors → Add custom connector → paste the URL.
- ChatGPT: add a custom connector (developer mode) with the URL and OAuth sign-in.
- Claude Code:
claude mcp add --transport http tradeping https://gettradeping.com/mcp
Clients without OAuth can send an API key instead, as Authorization: Bearer tp_live_…. Create keys in Settings → API keys.
Tools
| get_account | Plan, limits, usage this month, targeting and mailbox status. |
| list_leads | Leads in your feed with the signal, decision maker, verified email and drafted sequence. |
| get_lead | One lead with its drafts, status and sequence step. |
| find_leads | Runs today's lead feed. Each verified lead counts toward your monthly allowance. |
| update_lead | Edit drafts or set a lead's status (approved, skipped, replied). |
| rewrite_lead | AI rewrite of a lead's three-step sequence. Uses one rewrite from your allowance. |
| send_lead | Sends the next step from your own mailbox, within your daily send cap. |
| list_suppressions | Addresses that will never be emailed from your account. |
| add_suppression | Block one or more addresses. |
Lead research runs a minute or two; find_leads returns what it found so far and you call it again to continue. Sending always asks you first in well-behaved assistants, and the server enforces your caps either way.
REST API
Base URL https://gettradeping.com/v1, JSON in and out, your API key as a Bearer token. Every route runs the same operation as the matching MCP tool.
| GET /v1/me | get_account |
| GET /v1/leads?status=new | list_leads |
| GET /v1/leads/{id} | get_lead |
| POST /v1/runs | find_leads |
| PATCH /v1/leads/{id} | update_lead |
| POST /v1/leads/{id}/rewrite | rewrite_lead |
| POST /v1/leads/{id}/send | send_lead |
| GET /v1/suppressions | list_suppressions |
| POST /v1/suppressions | add_suppression |
curl https://gettradeping.com/v1/leads?status=new \ -H "Authorization: Bearer $TRADEPING_KEY"
curl -X PATCH https://gettradeping.com/v1/leads/LEAD_ID \
-H "Authorization: Bearer $TRADEPING_KEY" -H "Content-Type: application/json" \
-d '{"status":"approved"}'Limits
API and MCP use your plan: Free 15 verified leads a month, Starter 500, Pro 1,800, with the same AI-rewrite allowance and daily send cap as the app. Requests are limited to 120 a minute per account. Agents can read skill.md for a short guide to working the feed; directories can read the server card.