# Your objects, your pages and your leads, at Claude's command

Connect your LeadTap.me account to the assistant you already use. Point your keychains, sign holders and QR codes wherever you want, build the pages they open and ask about your leads. In your own words, from one connector.

- Overview page: https://www.leadtap.me/en/mcp
- Developer documentation (authentication, tool catalog, plan gates, errors): https://docs.leadtap.me/
- Server URL: https://app.leadtap.me/api/mcp
- Server version: 0.10.0 · Last updated: 2026-10-13
- Claude Code plugin and skills: https://github.com/dfla9701/leadtapme-claude
- Portal: https://app.leadtap.me/ · Store: https://app.leadtap.me/store
- Privacy: https://app.leadtap.me/privacy-policy · Terms: https://app.leadtap.me/terms-of-service

## Add LeadTap.me to Claude

In claude.ai or Claude Desktop: Settings, Connectors, Add custom connector. Paste this address, sign in to LeadTap.me and allow access: read, or read and write. You decide.

Server address: `https://app.leadtap.me/api/mcp`

## Add LeadTap.me to Claude Code

Two commands install the plugin: the server and four skills that teach Claude to build pages, schedule objects by the hour, connect webhooks and review the week. On the first action, the browser asks you to sign in to LeadTap.me and allow.

```bash
claude plugin marketplace add dfla9701/leadtapme-claude
claude plugin install leadtap@leadtap
```

To update: `claude plugin update leadtap@leadtap`. Server only, without the skills: `claude mcp add --transport http leadtap https://app.leadtap.me/api/mcp`. Repository: https://github.com/dfla9701/leadtapme-claude

## Add LeadTap.me to your own agent

Cowork, Cursor or your own agents: any MCP client. It is a remote server over Streamable HTTP, with OAuth 2.1 or an API token you create in Account & Billing. The details for integrators are in the docs.

Server address: `https://app.leadtap.me/api/mcp`

Revoke access any time from Account & Billing, in the portal.

## Command your NFC objects and QR codes from Claude

Keychains, sign holders, touchpoints and QR codes: where they lead, be it your lead page or any link, your website or your Instagram; on what schedule; and a new one ready to print. No other NFC object or QR code works this way.

### Change where every tap leads

The keychain doesn't change; its destination does: your lead page or any link, your website or your Instagram. To the promo today and back to your card whenever you want, in one sentence.

> **You:** Point my keychain to the spring promo page. Go ahead.
>
> **Claude:** Done. Your keychain now opens "Spring promo" on the next tap. It used to open your digital card; say the word and I switch it back.
>
> Destination: Spring promo · Before: digital card · Live on the next tap

### Schedule them by the hour

The lunch menu on weekdays at noon and the dinner menu the rest of the time. Claude sets up the week in your time zone. From Plus.

> **You:** Send the entrance QR to the lunch menu on weekdays from 12 to 4, and to the dinner menu the rest of the time.
>
> **Claude:** Done. The entrance QR opens the lunch menu Monday to Friday, 12:00 to 16:00, and the dinner menu the rest of the week, in your time zone. It takes effect on the next scan. Nothing to reprint.
>
> Schedule applied · 5 slots · Fallback: dinner menu · Live on the next scan

### A lifetime QR code, ready to print

Ask for it and you get it with a code from your pack. The printed code never changes; where it leads, whenever you want.

> **You:** Create a QR code for the shop window that opens the spring promo page, and give me the file to print.
>
> **Claude:** Done. "Shop window" is ready and opens "Spring promo"; it used one of your bought codes, so you have 3 left. Here is the file to print. The printed code never changes: point it anywhere later.
>
> QR created · 3 codes left · Opens: Spring promo · Print file ready

**What changes for you**

- **Every tap, wherever you say.** Change where a keychain, a sign holder, a touchpoint or a QR code leads in one sentence. Claude confirms with you and the object obeys on the next tap.
- **By the hour, in your time zone.** One slot per link, a night window as two slots, a fallback link. Claude proposes it, checks for overlaps and shows you the week.
- **Nothing to reprint.** The printed QR code and the encoded object never change. What they open, as many times as you want.

## Build the page every object opens

Describe what you offer and what you want to capture, the way you would tell a person. Claude builds the page, reviews it with you and publishes it when you say so.

### The page that presents your business

Who you are, your contact card to save and the prospect's email. Connected to your keychain in the same request.

> **You:** Connect this keychain to a page that presents my business, lets people download my contact card and asks for their email. Publish it when it's ready.
>
> **Claude:** Done. "Vista Norte · Meet Alba" is live: who you are and what you do, a Save contact button with your card, and one question, their email. The keychain opens it on the next tap, and every email lands in your leads.
>
> Page published · 3 steps · Save contact · your vCard · Keychain live on the next tap · Every email in your leads

### The menu for the table QR codes

Starters, mains and desserts with photos, and a booking button at the end. The table QR code opens it.

> **You:** Build a menu page for the QR on the tables: starters, mains and desserts with photos.
>
> **Claude:** Here is the draft of "Our menu": three sections with stock photos where yours will go, and a "Book a table" button at the end. Want to see the preview, or should I publish it and point the table QR codes to it?
>
> Draft saved · 3 sections · Preview link ready · Waiting for your OK to publish

### The open house sign-in

The property, the visitor's details, whether they have an agent and when they want to buy, with scoring; your card at the end.

> **You:** An open house sign-in for Saturday: the property, the visitor's details, whether they have an agent and when they want to buy, and my card at the end.
>
> **Claude:** Drafted "Open house · 12 Main Street": the listing, name and verified email, agent yes or no, timeline (now, 3 months, 6 months, just looking) and your card as the ending. Buying now without an agent scores highest. Publish it and point your sign holder to it?
>
> Draft saved · 5 steps · Scoring: timeline + agent · Waiting for your OK to publish

**How it works**

- **Describe it like you would to a person.** What you offer and what you want to capture. Claude picks the steps that work on a phone: presentation, card, question, email, reward.
- **You review it before publishing.** It shows you the draft and the preview. Publishing needs your confirmation: it puts the page in front of the public and uses quota.
- **Your work stays yours.** What you edited in the portal is respected. Claude changes only what you ask for and tells you what changed.

## Your leads, where you already work

Who filled in what, with their score; every lead in your CRM through a webhook; and the weekly review. Ask, and it tells you.

### Ask about your leads

"Who filled in the fair form?" With their answers, their score and who to call first.

> **You:** Who filled in the fair form this week, and who should I call first?
>
> **Claude:** Twelve people since Monday. Call Carlos Ibáñez first (score 100: buying within 3 months, no agent, verified email), then Marta Quesada (100) and Nerea Castaño (88). Four were just looking; I can list them if you want.
>
> 12 leads · fair form · 3 hot · verified emails · Call list ready

### Every lead, to your CRM

A CRM webhook to Zapier, Make, n8n or your own. Claude creates it and tests it; you turn it on. From Plus.

> **You:** Send every lead in my account to my CRM through this Zapier URL.
>
> **Claude:** Created the CRM webhook to your Zapier URL for new, verified and updated leads, and sent a test: Zapier answered 200. It starts off, as every new webhook does; you have an email to turn it on in the portal.
>
> CRM webhook created · Test delivered · 200 OK · Off until you turn it on

### The weekly review

Numbers first, then people, and one or two concrete actions at the end.

> **You:** How did my lead pages do this week, and who should I call?
>
> **Claude:** Taps 214, visits 190, submissions 41, verified leads 33. The open house page converts best; the menu page loses people at the email step. Call Carlos Ibáñez and Marta Quesada today. One action: make the email step on the menu page optional.
>
> 33 verified leads · 2 calls today · 1 action suggested

**What it knows about your leads**

- **With their score.** Who filled in what, their answers, their verified email and their score, without opening the portal.
- **And from there, wherever you work.** The CRM webhook sends every lead to your CRM, to Zapier, Make, n8n or to an AI workflow. It starts off: you turn it on in the portal.
- **The week at a glance.** Taps, visits, submissions and leads; where people drop off; who to call and why.

## You have the last word

- **Asks before publishing.** Publishing a page, changing a link, moving an object or spending a QR code: Claude confirms with you first.
- **Never deletes or buys.** It cannot delete anything or pay for anything. To buy, it gives you the link and you do it, in your own session.
- **Only your account.** It acts only on the account you gave it permission for, and you can revoke it at any time. What your leads type is treated as data, never as instructions.
- **On every plan.** It comes with your account, Free included. What it can do inside follows your plan, the same as in the portal.

## Server facts

| | |
|---|---|
| Server URL | https://app.leadtap.me/api/mcp |
| Server name and version | leadtap / 0.10.0 |
| Tools | 34 (17 read-only, 17 write) |
| Transport | Streamable HTTP, MCP protocol 2025-06-18 |
| Authentication | OAuth 2.1 (recommended) or API token (ltp_…) |
| Scopes | read and 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 |
| 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 |

## How authentication works

- **Two credentials.** OAuth 2.1 for apps (claude.ai, Claude Code with the browser flow): you sign in on app.leadtap.me, see which app is asking and which scopes, and allow or deny. API tokens (ltp_…, created in Account & Billing, Claude & API) for scripts and headless clients: they carry both scopes and the full token is shown once.
- **OAuth details, for integrators.** Authorization server metadata at app.leadtap.me/.well-known/oauth-authorization-server; protected-resource metadata at app.leadtap.me/.well-known/oauth-protected-resource. Public clients only, PKCE S256 required, dynamic client registration (/api/oauth/register) and client-ID metadata documents (an https URL as client_id). Authorization codes last 10 minutes and are single-use; access tokens (lta_…) last 1 hour; refresh tokens (ltr_…) last 30 days and rotate, and reusing an old one revokes the whole grant. Revocation at /api/oauth/revoke (RFC 7009). A request without a valid credential gets 401 with WWW-Authenticate pointing at the resource metadata, which is how clients discover the flow.
- **Scopes.** read for the read-only tools; write for everything that creates or changes. A read-only authorization gets INSUFFICIENT_SCOPE on write tools.
- **What the server never does.** It never acts on an account other than the credential's. It never deletes anything (no delete tools in v1). It never buys anything: store tools give links, the purchase happens in the portal in the customer's own session. It never turns a webhook on: a webhook created or re-pointed by an agent starts off, the account owner gets an email, and only the owner turns it on in the portal. It answers only the client that asked, with that account's data, and sends nothing to any third party.
- **Lead data is data.** Answers, names and notes typed by your leads are returned as data; the server tells Claude to treat them as data, never as instructions.
- **Operations.** 60 calls per minute per credential. Every call is logged (account, credential, tool, success or error code, duration) for support; never the arguments or the results. Expired OAuth codes and tokens are purged daily.
- **Confirmation before writes.** The server marks every write tool so Claude asks before saving a draft, publishing, pausing a page, changing a link, changing where an object sends people, or spending a bought QR code. Publishing a page makes it public.

## Skills and the Claude Code plugin

The MCP server gives Claude the actions; the skills give it the craft. They are plain Markdown and only use the server's tools, so they work on any account. The server works without them; with them, Claude builds pages and webhooks the way the portal expects. The same skill folders upload to claude.ai as custom skills (Settings, Skills).

| Skill | What it teaches Claude | Use it when |
|---|---|---|
| `lead-pages` | Building, editing and publishing pages of any mix: a lead capture form, a digital contact card, a business presentation (about us, products & services, testimonials), a menu, a review flow, a qualifier, an RSVP, and mixes like an open house sign-in, a hotel's experiences page, a tour agency or a remodeling company's portfolio with a quote request. The steps that work on a phone, how endings and redirects really behave, scoring and outcomes without gaps, stock photos and where the customer replaces them (own work with own photos), review flows that do not gate, and never overwriting what the customer edited in the portal. | Creating, changing, reviewing or publishing any LeadTap.me page, form, card, menu or landing page, or when a draft comes back with issues. |
| `smart-routing` | Reading where a Smart Object sends people, proposing a weekly schedule by link, checking overlaps, applying it and showing the week back. Days and hours in the customer's time zone, a night window as two slots, a fallback link. | Changing an object's destination, routing a QR or NFC by hours or days, reviewing or optimising smart routing. |
| `webhooks` | Sending leads out. The CRM webhook (every lead, every page, to an external CRM, an AI agent workflow, Zapier, Make, n8n or the sales team) and the page webhook (one page's submissions, for a sheet or statistics): which one to offer, the flow (it starts off; the account owner turns it on in the portal after an email), what the receiver gets (both JSON bodies, headers, the HMAC signature, the 10-second window, retries) and reading the delivery log. | Connecting leads to a CRM, a workflow, an agent, Slack, a sheet or a URL; setting up or checking a webhook; "did my CRM get the lead?". |
| `weekly-leads` | The weekly review: numbers first (taps, visits, submissions, leads, drop-off per step, delivery failures), then people (who to call and why), then one or two concrete actions. | "How is it going?", a weekly or monthly summary, what happened with a page, who filled it in, which leads to follow up. |

## Questions about the MCP

### Does LeadTap.me have an MCP server?

Yes. It works with claude.ai, Claude Desktop, Claude Code, Cowork and any MCP client. The server address is on this page and the technical details are in the docs.

### Does the MCP cost anything?

No. It comes with every LeadTap.me account, Free included. What you can do inside follows your plan's features and quotas, the same as in the portal.

### What can Claude do with it?

Create, edit and publish pages; read submissions and contacts; create and update links; rename objects and change where they send people, including by schedule; read your numbers; create a QR code with a bought code; and tell you what the store sells and where to buy it.

### What can it not do?

Delete anything, buy anything, act on another account, route by browser language, or bypass your plan's limits.

### Is my data safe?

Every action is taken only on the account that gave permission. Writing needs the write permission and Claude asks first. You can revoke access any time from the portal. Your leads' answers are returned as data, never as instructions.

### What is the server address and how does it authenticate?

https://app.leadtap.me/api/mcp, a remote server over Streamable HTTP (MCP protocol 2025-06-18). Authentication with OAuth 2.1, the recommended way: you sign in on app.leadtap.me, see which app is asking and which scopes, and allow or deny. Or with an API token created in Account & Billing, for scripts and headless agents. Two scopes: read and write. The details for integrators are in the docs.

### How many tools does it have?

Version 0.10.0 has 34: 17 read-only and 17 write. Each one acts only on the account behind the credential, at 60 calls per minute. The full catalog, with every description exactly as Claude receives it, is in the docs.

### How do I connect from claude.ai?

Settings, Connectors, Add custom connector; paste the server address; sign in to LeadTap.me and allow.

### How do I connect from Claude Code?

With the plugin, which brings the skills: "claude plugin marketplace add dfla9701/leadtapme-claude" and "claude plugin install leadtap@leadtap". Server only: "claude mcp add --transport http leadtap https://app.leadtap.me/api/mcp".

### Is there a plugin or skills for Claude?

Yes, public at github.com/dfla9701/leadtapme-claude: a Claude Code marketplace with the MCP server and four skills (lead-pages, smart-routing, webhooks and weekly-leads). The same skill folders upload to claude.ai as custom skills. The server works without them; with them, Claude builds pages and webhooks the way the portal expects.

### Can Claude publish a page without asking?

No. Publishing needs your confirmation: it puts a page in front of the public, uses quota and may start your 14-day Plus trial.

### Can it set up webhooks?

Yes, on Plus, and there are two kinds. The CRM webhook sends every lead in the account (new lead, verified, new submission) to your own CRM, an AI agent workflow, Zapier, Make, n8n or your sales team: that is the one Claude offers when you want your leads somewhere. A page webhook sends one page's submissions, for statistics or a spreadsheet. Claude can create either, change its events, point it at a new URL, send a test, read the delivery log and retry failed deliveries. Every webhook it creates starts off; the account owner gets an email and turns it on in the portal. Claude never sees the full URL or secret again, and cannot delete it.

### Can it create QR codes or NFC objects?

A QR code, yes, if your account has a bought code left. NFC objects are physical: bought in the store, shipped to your door and connected with a tap.

### Can Claude point an object to my website or my Instagram?

Yes. An object or a QR code can open your lead page or any link. Claude creates the link (a short LeadTap.me URL that redirects wherever you say), points the object or a schedule slot at it and changes it later with nothing to reprint; it applies on the next tap. External links are unlimited on every plan. With an external link there is no data capture: that is what the lead page does.

### Which plan do I need for routing by schedule?

Plus or above. Reading a schedule works on every plan.


---

# Start free. Pay when you need more.

Every account publishes 3 pages for free, and each object you buy adds one more, for life. Plus and Ultra add power, capacity and depth.

Pricing page: https://www.leadtap.me/en/pricing

## Free: Free

Everything you need to capture leads with your objects.

## Plus: 49 USD per month, 490 USD per year

Scoring, webhooks and more pages for teams that qualify.

## Ultra: 89 USD per month, 890 USD per year

Your brand up front and the deepest analytics.

Try Plus for 14 days when you publish your first page. No card needed.
No plan caps responses.

## What each plan includes

| Feature | Free | Plus | Ultra |
|---|---|---|---|
| **Capacity** | | | |
| Lead pages | 3 + 1 per object | 20 + 1 per object | 100 + 1 per object |
| Responses per page | Unlimited | Unlimited | Unlimited |
| Connected NFC objects | Unlimited | Unlimited | Unlimited |
| Dynamic QR codes | Bought separately | Bought separately | Bought separately |
| Editable external links | Unlimited | Unlimited | Unlimited |
| **Lead page** | | | |
| Every question type | Included | Included | Included |
| Cover and card layout | Included | Included | Included |
| Redirect on completion | Included | Included | Included |
| Notification and confirmation emails | Included | Included | Included |
| Lead reward | Coupon | Coupon or file | Coupon or file |
| Your logo on the page | Not included | Included | Included |
| Scoring and flow rules | Not included | Included | Included |
| Partial submit | Not included | Included | Included |
| Page embedded on your site | Not included | Not included | Included |
| Share image for the link | Not included | Not included | Included |
| Saved brand theme | Not included | Not included | Included |
| No LeadTap.me branding | Not included | Not included | Included |
| **Capture and data** | | | |
| CRM and CSV download | Included | Included | Included |
| Webhooks to your CRM, Zapier, Make or n8n | Not included | Included | Included |
| Routing by schedule | Not included | Included | Included |
| Analytics history | 7 days | 60 days | 180 days |
| **Artificial intelligence** | | | |
| AI credits to build pages | 10 as a gift when you sign up | 60 a month | 250 a month |
| **In development** | | | |
| Custom domain | Not included | Not included | Coming soon |
| Tracking pixels | Not included | Not included | Coming soon |
| Teams and workspaces | Not included | Not included | Coming soon |
| Automatic translation | Not included | Not included | Coming soon |