Skip to content

What each LeadTap.me plan allows through the MCP server

The LeadTap.me MCP server reads and writes on every plan, Free included; what the plan decides is the same through Claude as in the portal. When a plan does not include something, the tool returns FEATURE_LOCKED or LIMIT_REACHED with an upgrade link.

Gate What it limits
Live lead pages How many lead pages can be live at once (the quota)
Paid page features Scoring, conditional logic, partial submissions, file rewards, brand theme, remove branding, custom domain, webhooks
Analytics window How far back analytics go: Free 7 days, Plus 60 days, Ultra 180 days
Smart routing Weekly schedules for Smart Objects: Plus or above. Reading a schedule works on every plan
Webhooks Creating a CRM or page webhook: Plus or above. Listing webhooks and their delivery log works on every plan

Analytics responses say clampedToPlan when a range was cut to the plan’s window, and Claude should never present a cut range as the whole history.

QR codes and NFC objects are bought, never included in a plan.

  • QR codes are bought once in packs, are dynamic for life, point to a lead page or any URL, and can be edited on every plan, Free included. With a bought code left, create_qr_code makes one.
  • NFC objects (keychain, sign holder, light touchpoint) are bought in the store, shipped, and connected by tapping them when they arrive.

Publishing a lead page with publish_form may start the account’s 14-day Plus trial on a first publication, the same as the Publish button in the portal.

Plan prices are on the pricing page. Object and QR pack prices are in the store, and Claude can read them with list_store_products.