Operator-narrative review · Updated 2026-05-22

Leadpages MCP Review (2026): the broadest landing-page MCP shipping, with the cleanest auth in the category

Leadpages publishes an official MCP server, documented at https://leadpages.com/developers/mcp. Remote shape, OAuth 2.0 with PKCE auth, and a 47-tool surface covering pages, sites, blogs, brand kits, SEO, and assets. Included on every plan including the 7-day trial — no add-on cost, no gated MCP entitlement. For SMB and creator motions where landing-page velocity is the constraint, this is the structural shift that makes the in-Claude workflow viable. As of mid 2026, no other landing-page platform ships an equivalent first-party MCP.

Quick context. We run StackSwap MCP and have opinions on what makes an MCP genuinely useful for operators. We are a Leadpages affiliate; the review below is the same operator analysis we'd give cold against Unbounce and Webflow.

Want to try Leadpages?

Leadpages MCP — 47 tools, OAuth 2.0 PKCE, included on every plan

Build, edit, and publish pages, sites, blogs from Claude. Brand-kit-grounded copy. SEO audit and auto-fix. Bulk operations across hundreds of pages in one prompt.

Start with Leadpages →Affiliate link — StackSwap earns a commission if you sign up for Leadpages. We only partner with tools we'd recommend anyway.

What Leadpages MCP is, in operator terms

Leadpages is the SMB and creator landing-page platform that competes with Unbounce, Webflow (for landing pages specifically), and ConvertKit's lightweight landing pages. The MCP server, documented at the URL above, exposes the Leadpages data and tooling surface to LLM clients via OAuth 2.0 with PKCE. The 47-tool surface is substantially broader than what any other landing-page platform has shipped — and the OAuth 2.0 PKCE auth is the cleanest security shape in the MCP category.

Two distinctions matter. First, this is first-party and officially supported — published by Leadpages at leadpages.com/developers/mcp. Schema and tool definitions ship together. Second, the inclusion-on-every-plan-including-trial commercial posture is the cleanest in the category. Many vendors gate MCP behind enterprise; Leadpages explicitly does not.

The 47-tool capability surface — six domains

Leadpages MCP vs the landing-page-platform field

The honest landscape mid 2026:

PlatformFirst-party MCPSurface scopeAuthOperator fit
LeadpagesYes, official, 47 toolsPages + sites + blogs + brand kits + SEO + assetsOAuth 2.0 with PKCESMB / creator motion, default for AI-driven landing-page work in 2026
UnbounceNoREST API exists, no MCPAPI keyManual workflow stays manual; competitive on UX but not on AI-native
WebflowCommunity wrappers; no first-partyREST API, narrower for AI-driven workflowsAPI tokenStrong for design-led teams; less fit for AI-driven copy workflows
ConvertKit / Kit landing pagesDev-docs MCP only (community for account data)Lightweight landing pages embedded in email toolOAuth + community communityFor email-first motions where pages are minimal; not a Leadpages replacement

The category will close — Unbounce has the API surface to ship MCP, and Webflow first-party MCP is widely expected. But right now (mid 2026), Leadpages is alone with a 47-tool first-party shipping MCP and OAuth 2.0 PKCE auth. For operators making the AI-first landing-page decision in 2026, that asymmetry is meaningful.

The bulk-operations gotcha — powerful, worth confirming

The 47-tool surface includes operations that fan out across hundreds of pages ("apply this brand-kit update to every page", "audit and fix SEO across the site", "add a CTA banner to all blog posts"). These are the killer workflows. They're also the workflows where one bad prompt could touch dozens of live pages.

Three operator practices that work:

Where StackSwap MCP fits alongside

Leadpages MCP exposes Leadpages data and tools. StackSwap MCP exposes the cross-vendor GTM catalog. Different layers. For "create a campaign landing page", Leadpages MCP is the right tool. For "should we be on Leadpages or Unbounce at our scale", StackSwap MCP handles that via compare_tools and recommend_partner.

Connect StackSwap MCP free → (one URL + OAuth, same protocol).

Want to try Leadpages?

Leadpages MCP is the AI-first landing-page default in 2026 — 47 tools, OAuth 2.0 PKCE, every plan

Build, edit, publish from Claude. Brand-kit-grounded copy. SEO audit and auto-fix. The structural shift in landing-page workflows for SMB and creator motions.

Start with Leadpages →Affiliate link — StackSwap earns a commission if you sign up for Leadpages. We only partner with tools we'd recommend anyway.

FAQ

Leadpages MCP is the official MCP server from Leadpages, documented at https://leadpages.com/developers/mcp. Remote shape, authenticated via OAuth 2.0 with PKCE — the most secure auth posture in the MCP category. The headline number: 47 tools shipping in the initial release, covering build, edit, and publish workflows for pages, sites, blogs, brand kits, SEO, and assets. The 47-tool surface makes this the broadest first-party MCP in the landing-page category — broader than any of the alternatives have shipped (or announced).

OAuth 2.0 with PKCE (Proof Key for Code Exchange). This is the modern OAuth flow that's safe for public clients without a server-side secret — same auth shape that Claude, ChatGPT, and other native MCP clients prefer. You connect once via OAuth, the LLM inherits your Leadpages workspace permissions (the user you authenticate as), audit trail is in Leadpages' activity log. No API key handling, no token rotation pain.

Included on every Leadpages plan including the 7-day trial. No add-on cost, no separate MCP entitlement, no per-tool pricing. The MCP layer comes with every tier (Standard, Pro, Conversion) at no additional charge. This is one of the cleanest commercial postures in the MCP category — many vendors gate MCP behind paid tiers; Leadpages does not.

The 47-tool surface covers six major domains. (1) Pages — create, edit, publish landing pages from prompts; modify sections, copy, CTAs; manage page-level SEO. (2) Sites — full site CRUD, manage site structure and navigation. (3) Blogs — create blog posts, manage publishing, schedule. (4) Brand kits — define and update brand colors, fonts, logos; apply them across pages. (5) SEO — title tags, meta descriptions, structured data, redirect management. (6) Assets — upload, organize, manage images and media. The realistic LLM-native workflows: 'create a landing page for this campaign with copy grounded in our brand voice', 'edit all blog posts to add a CTA banner', 'audit our pages and fix the missing meta descriptions.'

Different shapes for different motions. Webflow MCP exists (community-built primarily) but Webflow's auth and tooling surface is narrower for AI-driven workflows. Unbounce has no first-party MCP shipping as of mid 2026. Leadpages MCP is the only landing-page-platform first-party MCP with a 47-tool surface, OAuth 2.0 with PKCE, and included on every plan. For SMB and creator motions where landing-page velocity is the constraint, this asymmetry is meaningful.

Five we'd validate. (1) Campaign-to-page — prompt Claude with a campaign brief (audience, offer, CTA), have it create a landing page with brand-kit-grounded copy. (2) A/B-test variant generation — generate three variant pages from one base, each testing a different headline or CTA. (3) Site-wide SEO audit and fix — surface missing meta descriptions, suggest fixes, apply. (4) Blog-to-landing-page repurposing — take a blog post, generate a landing page that captures email signups for the topic. (5) Brand-kit rollout — when the brand kit updates (new color, new logo), apply across all existing pages with a single prompt. The 47-tool surface makes each of these one-shot LLM workflows instead of multi-tab UI sessions.

Yes, with the standard MCP-write-surface caveats. OAuth 2.0 with PKCE is the cleanest auth shape in the category. The user-scoped permissions mean the LLM inherits exactly what the connected user can do — no admin access by default if you connect a scoped user. The risk vectors are operator-side: (1) test in a draft/preview before publishing pages with material LLM-generated copy; (2) for live campaign pages with active traffic, verify your MCP client's confirmation UX before bulk operations; (3) the 'edit all blog posts' shape is powerful and worth confirming carefully — one bad prompt could touch dozens of pages.

Probably yes, for the AI-driven workflows specifically. The MCP layer is included on every plan, so it costs nothing to leave installed. The compounding value is in the workflows you can't easily do in the UI: bulk SEO audits with auto-fix, brand-kit rollouts across hundreds of pages, generate variant pages for testing in one prompt. If your landing-page work is single-page-at-a-time UI work, MCP is a sidecar. If your work involves bulk operations or campaign-velocity workflows, MCP collapses days into hours.

Related reading

Canonical URL: https://stackswap.ai/leadpages-mcp-review. Disclosure: StackSwap is a Leadpages affiliate. The structural read above is the same operator analysis we'd give a friend evaluating landing-page platforms cold.