Leadpages business MCP pilot

Bring your agent. Find your next step.

Your conversation is the brief. Ask about your business needs and your agent can compose a page of answers, comparisons, estimates and next steps—then evolve the same page as your questions change.

In clients that support MCP Apps, view the tailored page in the conversation, then choose “Continue on website.” Other clients receive structured content and a labeled link. An arbitrary URL does not automatically embed or open a browser tab.

Pilot status: Not enabled on this deployment yet. The endpoint returns 404 until the pilot is enabled.

A separate connection for exploring Leadpages

This is for prospective buyers. It is not the authenticated page-management MCP, and cannot access your account, publish pages, or change your subscription.

  1. In a compatible agent client, add a new remote MCP connection using Streamable HTTP.
  2. Use endpoint https://leadpages.com/api/business-mcp.
  3. No OAuth or Leadpages login is required. Approve the connection and any tool calls your agent host asks you to authorize.
  4. Ask your agent to clarify your requirements, recommend a plan, and create a preview. Open the returned link if your host does not open it automatically.

Server-side agent clients are supported. Cross-origin browser integrations are not enabled in this pilot.

“How could Leadpages work for my agency? Build me a page answering that.” Then: “Compare two approaches, add an estimate for my requirements and a way to talk to sales.”

What the pilot can do

Estimates use USD base catalog prices, excluding tax, add-ons, promotions and localization. Annual estimates are yearly totals. Pricing and checkout remain authoritative. Unsupported requirements need confirmation from sales.

Discovery is not permission

We link this page from our homepage footer and publish the endpoint in llms.txt. These help people and agents find documentation; they do not guarantee automatic discovery, connection, or permission to act.

An optional AI catalog pointing to an MCP Server Card is a later discovery layer, not part of this pilot. It is an emerging approach and client support varies.

Keep previews non-sensitive

Anyone with the preview link can read it until it expires. Read access and edit access use separate random capabilities. Your agent must keep its edit token private and share only the read URL. Do not put names, email addresses, account details or confidential information in your requirements.

No arbitrary HTML is generated or executed. The agent cannot submit inquiries, schedule meetings, or handle payments. You can submit your own inquiry using the separately enabled sales form; personal details stay out of the shared preview.

The server receives only the inputs your agent passes to a tool, not your entire conversation. The embedded view uses a registered, reusable UI resource; it does not load a customer-specific URL into the conversation.