LeadTap.me MCP server: connect Claude to your account
The LeadTap.me MCP server lets Claude (claude.ai, Claude Desktop, Claude Code, Cowork) and any MCP-compatible client work on your LeadTap.me account: build and publish lead pages, read your CRM, send every lead to your own CRM, an AI agent workflow or your sales team by webhook, create and update links, route NFC objects and QR codes by schedule, read analytics and see what the store sells. It is a remote server at https://app.leadtap.me/api/mcp (Streamable HTTP), authenticated with OAuth 2.1 or an API token, and it acts only on the account that owns the credential.
LeadTap.me MCP server at a glance
Section titled “LeadTap.me MCP server at a glance”| Fact | Value |
|---|---|
| Server URL | https://app.leadtap.me/api/mcp |
| Transport | Streamable HTTP (stateless, no sessions) |
| Server name / version | leadtap / 0.10.0 |
| Tools | 34 (17 read-only, 17 write) — full catalog |
| Auth | OAuth 2.1 (recommended) or API token (ltp_…) — how it works |
| Scopes | read, write |
| Rate limit | 60 calls per minute per credential; 429 with Retry-After |
| Response cap | 100,000 characters per response; above that, a truncation notice, never a cut JSON |
| Plans | Read and write on every plan, Free included. Feature gates are the product’s own — plan gates |
| Data | Every tool acts on the account behind the credential; nothing is shared across accounts |
| Domains | Portal app.leadtap.me; public lead pages page.leadtap.me; object redirector tap.leadtap.me |
What Claude can do on LeadTap.me
Section titled “What Claude can do on LeadTap.me”Claude can do through the MCP server what you do in the portal, except deleting and buying.
- Lead pages: create a page, write its draft, publish it, pause or resume it, rename it. See lead pages.
- CRM: list the submissions of a page, list contacts, read everything one person answered.
- Links: list, create and update external links.
- Smart Objects: rename them, point them at one link, or give them a weekly smart routing schedule; create a QR code with a bought code.
- Webhooks: add the CRM webhook, which sends every lead in the account to a CRM, an AI agent workflow, Zapier, Make, n8n or a sales team, or a page webhook for one page’s data; change or turn either off, send a test, read the delivery log and retry failed deliveries. A new webhook starts off until the account owner turns it on. See webhooks.
- Analytics: a page’s funnel and completion rate, taps and scans per object, the portal’s home numbers.
- Store: what LeadTap.me sells, at what price, and the link to buy it.
What the LeadTap.me MCP server does not do
Section titled “What the LeadTap.me MCP server does not do”The server never deletes, never buys, never turns a webhook on and never acts on another account.
- It has no delete tools.
- Store tools give links; the purchase happens in the portal, in the customer’s own session.
- It never turns a webhook on: a webhook Claude creates or points at a new URL starts off, the account owner gets an email, and only the owner turns it on in the portal.
- It does not route by browser language.
- It does not bypass a plan gate: what the plan does not include returns an error with a link to upgrade.
How to start
Section titled “How to start”Connect Claude in one step: add https://app.leadtap.me/api/mcp as a custom connector and allow access. Full steps for every client are in how to connect Claude to LeadTap.me. The first thing Claude does is call get_account to learn your plan, its features and quotas before proposing anything.