MCP Server
Updated 2026-10-06
In short
The Leadpages MCP server gives AI assistants the ability to build, publish, edit, and manage landing pages, sites, blogs, and brand kits on your behalf.
Connect AI assistants to Leadpages via the Model Context Protocol. Build, manage, and optimize landing pages from Claude, Cursor, n8n, or any MCP-compatible client.
https://mcp.leadpages.com/mcp- 47 tools
- OAuth 2.0 with PKCE
- No API keys needed
- Works everywhere
Instead of switching between chat and a page builder, your AI assistant does it all in one conversation.
Who is this for?
Marketers, founders, and teams who want to build high-converting landing pages faster. Tell Claude what you need in plain English and get a live, published page in seconds. No code required.
How it works.
The MCP server exposes 47 tools that your AI assistant can call during a conversation. When you say "build me a landing page for my webinar", the assistant generates the HTML and calls create_page to publish it instantly. One server works across Claude.ai, ChatGPT, Claude Desktop, Claude Code, Cursor, n8n, and any MCP-compatible client.
Authentication
The MCP server uses OAuth 2.0 with PKCE to authenticate with your Leadpages account. When you connect for the first time, your AI client will open a browser window for you to sign in and authorize access.
No API keys, tokens, or secrets to manage. Your session stays active across conversations. If it expires, you will be prompted to re-authorize.
- Your MCP client sends a connection request to the server
- The server redirects to Leadpages OAuth consent screen
- You sign in and authorize the connection
- The server receives tokens via PKCE flow (no client secret needed)
- All subsequent tool calls use the authorized session
Scopes. The MCP server requests access to manage pages, sites, blogs, assets, and brand kits on your behalf. You can revoke access at any time from your Leadpages account settings.