How to connect LanderLab 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": {
"landerlab": {
"command": "npx",
"args": ["-y", "<server-package-name>"],
"env": {
"LANDERLAB_API_KEY": "your-api-key-here"
}
}
}
}
// Server source: https://landerlab.io/mcp
// Check the server's README for the exact "command" and required env vars.Some MCP servers require an API key. Check the source page for setup: landerlab.io/mcp.
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 subscription pricing
| Plan | Monthly | Annual / mo |
|---|---|---|
| Launch | $129 | $69 |
| Grow | $149 | $119 |
| Scale | $299 | $239 |
| Enterprise | $799 | $639 |
Source: landerlab.io/pricing. Scraped 2026-05-19.
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 changed 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.
- Auth flow: MCP servers usually inherit the underlying API auth method (unknown). 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 LanderLab API quota. Burst usage from a curious agent can drain a daily allowance fast.
Agent-readiness verdict
Good agent fit with official MCP support. LanderLab offers an official MCP server and documented OpenAPI spec, giving Claude workflows direct access to its landing page builder and template system. The lack of webhooks and structured outputs limits real-time automation and response parsing, so you'll need custom parsing logic for complex workflows.
Scored 2026-05-19 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 have a public API?+
Does LanderLab publish an OpenAPI / Swagger spec?+
Sources
- LanderLab official site: https://landerlab.io/
- MCP server page: https://landerlab.io/mcp
- API docs: https://landerlab.io/api
- Pricing source: https://landerlab.io/pricing/ (scraped 2026-05-19)
Data verified by Joonas on the dates shown. MCP server status auto-rechecked weekly.

