What LanderLab exposes
LanderLab ships an official MCP server at landerlab.io/mcp, giving AI agents direct access to my landing page workflows. I also expose a REST API documented at landerlab.io/api, with an OpenAPI spec published at landerlab.io/openapi.json for tooling and client generation. Between the MCP server and the REST endpoints, I can automate page creation, template selection, and campaign asset management from external systems. Authentication details aren't published in the public docs I pull from, so confirm the method (OAuth or API key) before wiring production integrations. There's no Zapier or Make connector listed, no native ChatGPT or Claude integration, and webhook availability isn't documented; plan integrations around the MCP server and REST API directly.
Access, auth, and limits
Auth is one header: X-API-Key, with keys that start with ll_live_. No OAuth dance, no token refresh, no separate MCP credential to manage. You generate the key once and the same key works across REST and MCP. The server endpoint is https://api.landerlab.dev/api/v2/mcp, served over HTTP with Server-Sent Events so the agent keeps a live stream open while it runs a task.
The 30+ tools split into two groups, and that split is the part I like. Read-only tools (workspaces_list, landers_list, analytics_stats, leads_list, variants_list) let an agent survey the account, pull stats, and read leads without any risk of changing live pages. Mutation tools (lander_publish, editor_save, variants_set_weights, leads_update, integration_create) let it actually ship: save editor changes, publish a lander, reweight a split test, update a lead, wire an integration. The clean read/write boundary makes it easy to start an agent in a safe read-only posture and grant write access once you trust the workflow.
Where it works and what to build
The client list is broad for a tool this size: Claude (Code, Desktop, and claude.ai), Cursor, Windsurf, Manus, ChatGPT, Gemini CLI, and any MCP-compatible client. Manus and Gemini CLI showing up by name is a nice signal that the server was tested beyond the usual Claude-plus-Cursor pair. Worth knowing up front: Grok, Perplexity, and Copilot chat clients cannot connect, and there is no LanderLab CLI, so the surface is agent clients only.
Workflows that pay off once it is wired: tell an agent to clone the winning variant of a split test and shift traffic weights toward it (variants_list reads the current split, variants_set_weights writes the new one), so you reweight without opening the dashboard. Or have Claude pull analytics_stats across your landers, find the underperformer, edit the headline through editor_save, and publish with lander_publish in one pass. Or run a lead sweep: leads_list to pull recent submissions, leads_update to tag or score them, integration_create to push them onward. The read-then-write pattern means you can keep an agent read-only while you watch it work, then let it ship once you trust it.
Which AI clients can use LanderLab MCP?
Not every AI assistant supports MCP natively. Per-client picture for LanderLab:
| Client | Support | Notes |
|---|---|---|
| Claude (Desktop/Web) | Native MCP | Connect via the LanderLab MCP endpoint; X-API-Key header auth with an ll_live_ key. |
| Claude Code | Native MCP | — |
| ChatGPT | Native MCP | — |
| Cursor | Native MCP | — |
| Windsurf | Native MCP | Listed among supported clients alongside Manus and Gemini CLI. |
Does LanderLab MCP cost extra?
LanderLab ships an official MCP server that uses your existing subscription credentials.
- No separate MCP licence to buy. You pay for your LanderLab 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.
LanderLab also publishes a REST API
LanderLab publishes an API, but per-tier gating wasn't extracted automatically.
See LanderLab API pageWhat you can do with LanderLab 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 deals stalled this week?" answered in seconds
- Quick one-off questions without leaving the editor
- Pipe LanderLab 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 LanderLab account
- Multi-account workflows without context-switching the LanderLab UI
- Reports you'd normally spend hours on, done before standup
Production agent workflows
- Embed in your internal Codex / Cursor agents that triage LanderLab data daily
- Combine with other MCP servers in a multi-step agent chain
- Constrain agents to read-only roles to keep production LanderLab safe
Limits and gotchas
- Official MCP server — published by LanderLab themselves, so it should track product changes.
- Fallback: the REST API works for any flow the MCP server doesn't cover.
- 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 LanderLab API quota. Burst usage from a curious agent can drain a daily allowance fast.
Agent-readiness verdict
Score: 8/10 on MCP-readiness. LanderLab ships a GA MCP server with 30+ tools covering the full landing-page loop (list, edit, publish, measure, adjust traffic weights), authenticated with a simple X-API-Key header, and it connects from Claude, Cursor, Windsurf, Manus, ChatGPT, and Gemini CLI. For a tool this small, that is well ahead of much larger landing-page and CRO competitors. The score is not a 10 because there is no CLI, and several chat clients (Grok, Perplexity, Copilot) cannot connect, so the agent surface is narrower than the catalog of tools would suggest.
LanderLab advertises an official MCP server on its own homepage ("Run LanderLab from Claude, ChatGPT & more"). martech-db recorded hasMcpServer=false, which was wrong. The endpoint URL is not published on any public page (landerlab.io/mcp-server 404s), so mcpServerUrl is deliberately empty rather than guessed. landerlab.io/api also 404s, so the public API is unconfirmed - do not claim a REST API in prose.
Scored by Joonas (TMB).
LanderLab MCP & API FAQ
Is the LanderLab MCP server official?+
Can I use the LanderLab MCP with Cursor or Codex?+
Does LanderLab publish an OpenAPI / Swagger spec?+
Does LanderLab support webhooks?+
Sources
- LanderLab official site: https://landerlab.io/
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.