What Leadpages exposes
I get programmatic access to Leadpages through an official MCP server, a REST API, and native integrations with ChatGPT, Claude, Gemini, and Perplexity. My API covers landing pages, leads, forms, analytics, and account data, with OpenAPI spec published at leadpages.com/openapi.json. Authentication supports both OAuth and API keys, so I can pick session-based flows for user-facing apps or static keys for backend jobs. The MCP server at leadpages.com/developers/mcp lets my LLM agents query and manage pages directly without custom glue code. Zapier and Make connectors are available for no-code workflows across thousands of downstream apps. Webhook availability is not documented in my data, so I would confirm event delivery options against the developer docs before relying on push notifications.
Access, auth, and limits
Auth is OAuth 2.0 with PKCE, handled through a browser sign-in. There are no API keys to generate, paste, or rotate, which is the part I appreciate most: nothing sensitive sits in a plaintext client config waiting to leak. I authorize once in the browser, the client holds the token, and the agent is connected.
The endpoint is https://mcp.leadpages.com/mcp over HTTP, with an SSE transport offered specifically for n8n. The server exposes 47 tools grouped into Pages (9), Sites (3), Assets (8), Blogs (19), Brand Kit (5), and Utility (3), so an agent can reach almost every surface of the account in one connection.
Best part for budgeting: the MCP server is included on all three plans, Grow, Optimize, and Scale. No add-on, no separate API tier, no 'available on Enterprise' wall. If you have a Leadpages login, you have the MCP server.
Where it works and what to build
Supported clients cover the ones I actually use: Claude.ai, Claude Desktop, Claude Code, Cursor, ChatGPT (on a paid plan), and n8n, plus any MCP-compatible client. The breadth matters because I am not locked into one assistant; I wire the server once and reach it from whichever tool I am in that day.
Workflows worth running: tell Claude to spin up a landing page from a one-line brief and publish it, and it drafts the copy, assembles the page, and pushes it live without me touching the builder. Hand the agent a batch of blog topics and let it draft and publish posts directly to a Leadpages-hosted blog (19 of the 47 tools are blog-focused, so this is well covered). Or use the Brand Kit tools to enforce fonts, colors, and logos across a new microsite so everything stays on-brand without manual checking.
For recurring automation, the SSE transport into n8n lets me trigger page builds or content updates on a schedule or off an external event, then hand the heavier creative work to an LLM client when I want a human-in-the-loop pass before publish.
Which AI clients can use Leadpages MCP?
Not every AI assistant supports MCP natively. Per-client picture for Leadpages:
| Client | Support | Notes |
|---|---|---|
| Claude (Desktop/Web) | Native MCP | Connect via the Leadpages MCP URL; OAuth 2.0 PKCE browser sign-in, no API key. |
| Claude Code | Native MCP | Add the https://mcp.leadpages.com/mcp endpoint; same OAuth browser sign-in. |
| ChatGPT | Native MCP | Supported on a paid ChatGPT plan via custom connectors. |
| Cursor | Native MCP | Add the MCP server in Cursor settings; OAuth browser sign-in. |
| n8n | Native MCP | Use the dedicated SSE transport for n8n automation flows. |
How to connect Leadpages MCP to Claude Desktop
Add this block to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Cursor and Codex use a similar schema.
{
"mcpServers": {
"leadpages": {
"command": "npx",
"args": ["mcp-remote", "<YOUR_MCP_URL>"]
}
}
}
// HTTP-transport MCP. Get your <YOUR_MCP_URL> from the vendor dashboard.
// Server source: https://leadpages.com/developers/mcp
// Claude Code (one-liner): claude mcp add leadpages <YOUR_MCP_URL> --transport httpSome MCP servers require an API key. Check the source page for setup: leadpages.com/developers/mcp.
Does Leadpages MCP cost extra?
Leadpages ships an official MCP server that uses your existing subscription credentials.
- No separate MCP licence to buy. You pay for your Leadpages plan, the MCP server queries that account.
- Whether it's gated to a specific tier wasn't extracted automatically — verify the access requirements on the MCP page or pricing docs.
Leadpages subscription pricing
| Plan | Monthly | Annual / mo |
|---|---|---|
| HTML Pub - Starter | $10 | $8 |
| HTML Pub - Pro | $29 | $23.2 |
| HTML Pub - Business | $49 | $39.2 |
| Leadpages - Grow | $99 | $39.2 |
| Leadpages - Optimize | $199 | $159.2 |
| Leadpages - Scale | $399 | $319.2 |
Source: leadpages.com/pricing. Verified 2026-06-07.
Leadpages also publishes a REST API
Leadpages publishes an API, but per-tier gating wasn't extracted automatically.
What you can do with Leadpages from an AI agent
Three shapes of agent workflow. Pick the row that matches how you actually use Claude / Cursor / Codex day to day.
Skip the dashboard, ask Claude
- "What changed this week?" answered in seconds
- Quick one-off questions without leaving the editor
- Pipe Leadpages data into your personal notes / docs without writing a script
Run client analysis at agent speed
- Hand the MCP server to your team — every consultant can ask Claude about any client's Leadpages account
- Multi-account workflows without context-switching the Leadpages UI
- Reports you'd normally spend hours on, done before standup
Production agent workflows
- Embed in your internal Codex / Cursor agents that triage Leadpages data daily
- Combine with other MCP servers in a multi-step agent chain
- Constrain agents to read-only roles to keep production Leadpages safe
Limits and gotchas
- Official MCP server — published by Leadpages themselves, so it should track product changes.
- Fallback: the REST API works for any flow the MCP server doesn't cover.
- Auth flow: MCP servers usually inherit the underlying API auth method (both). Expect to configure that on first install.
- OpenAPI spec is published — easy to validate which endpoints the MCP server actually exposes vs the full API surface.
- Rate limits: MCP calls count against your underlying Leadpages API quota. Burst usage from a curious agent can drain a daily allowance fast.
Agent-readiness verdict
Score: 9/10 on MCP-readiness. Leadpages is one of the few landing-page builders with a generally-available MCP server that grants agents real write access: build, publish, edit, and manage pages, sites, blogs, and brand kits across 47 tools. Auth is OAuth 2.0 with PKCE and a browser sign-in, so there are no API keys to leak into a client config. It works across Claude.ai, Claude Code, Claude Desktop, Cursor, ChatGPT (on a paid plan), n8n, and any MCP-compatible client, and it ships on every plan rather than gating behind an enterprise tier. I am holding back the last point only because the toolset is young and the breadth of write access means I would test agent output carefully before letting it publish to a live, high-traffic page.
Strong agent-fit for Claude workflows. Leadpages has an official MCP server and documented public API with OpenAPI spec, enabling direct integration with Claude and ChatGPT. Missing webhooks and structured outputs limits real-time automation and data parsing capabilities.
Scored 2026-06-07 by Joonas (TMB).
Leadpages MCP & API FAQ
Is the Leadpages MCP server official?+
Can I use the Leadpages MCP with Cursor or Codex?+
Does Leadpages have a public API?+
Does Leadpages publish an OpenAPI / Swagger spec?+
Which LLMs does Leadpages integrate with directly?+
Sources
- Leadpages official site: https://www.leadpages.com/
- MCP server page: https://leadpages.com/developers/mcp
- API docs: https://leadpages.com/developers/docs
- Pricing source: https://www.leadpages.com/pricing (verified 2026-06-07)
Data verified by Joonas on the dates shown. MCP server status auto-rechecked weekly.
10+ years in digital marketing. I review marketing software for AI-stack fit: real pricing, MCP and API support, and how cleanly each tool drops into an AI agent workflow, cross-checked against verified data and real user feedback.

