Access, auth, and limits
Orbit, the Landingi MCP server, is in development, so there is nothing to authenticate against yet. Landingi markets Orbit as included on the Scale and Enterprise tiers, but it is not documented in the public REST API and I could not confirm a working endpoint, which means the auth method and connection URL are not yet settled. Treat the MCP path as announced, not available.
If you need an agent reaching Landingi today, you go through the REST API at api.landingi.com/v2 instead. That path is live and documented, and it covers the credentials and request flow you would actually use right now. I will document Orbit's real auth (login plus token, OAuth, whatever Landingi lands on) the moment the server ships with a connectable endpoint. Until then, plan your integration around the API.
Where it works and what to build
Here is what Orbit aims to enable, framed as the roadmap it is rather than a feature you can run. The pitch: from inside your LLM, ask for a landing page and have Lunar generate it, then pull Solis insights on how existing pages are performing, all without opening the Landingi dashboard. An agent would build, edit, and read pages through one conversation. That is the workflow Landingi is selling toward, and it is a sensible one for a page builder.
The catch worth repeating: none of that is connectable yet, because Orbit is still in development. So for an agent touching Landingi today, the workflow runs through the REST API at api.landingi.com/v2, with Zapier and Make handling the no-code side. You can trigger page actions, sync form leads to a CRM, or fire follow-up sequences when a landing page converts, all via those live paths. Build against the API now, and slot Orbit in once it ships with a documented endpoint. I will rewrite this section with concrete client steps the day that happens.
Does Landingi MCP cost extra?
Landingi has no verified MCP server.
- No published MCP integration was detected at the last check.
- For now, agent workflows depend on the REST API or third-party automation.
Landingi subscription pricing
| Plan | Monthly | Annual / mo |
|---|---|---|
| Build | — | $24 |
| Optimize | — | $119 |
| Scale | — | $229 |
| Enterprise | — | $1,199 |
Source: landingi.com/pricing. Verified 2026-05-31.
Landingi also publishes a REST API
Landingi publishes an API, but per-tier gating wasn't extracted automatically.
What you can do with Landingi 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 Landingi 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 Landingi account
- Multi-account workflows without context-switching the Landingi UI
- Reports you'd normally spend hours on, done before standup
Production agent workflows
- Embed in your internal Codex / Cursor agents that triage Landingi data daily
- Combine with other MCP servers in a multi-step agent chain
- Constrain agents to read-only roles to keep production Landingi safe
Limits and gotchas
- ⚠ Server unreachable on last check. May be down, moved, or auth-gated.
- Fallback: the REST API works for any flow the MCP server doesn't cover.
- Rate limits: MCP calls count against your underlying Landingi API quota. Burst usage from a curious agent can drain a daily allowance fast.
- No MCP available — until Landingi ships one, use the REST API directly.
Agent-readiness verdict
Score: 5/10 on MCP-readiness. I am giving credit for two real things: a published MCP roadmap (Orbit) and existing AI tooling (Lunar for page generation, Solis for insights) that gives Orbit something genuine to expose. But the score caps here because Orbit is not shippable today. There is no documented endpoint, no confirmed auth, and nothing in the public REST API that an agent can connect to right now. The usable path today is the API, not MCP. Once Orbit has a live, documented endpoint, this number moves.
Avoid for agent workflows. Landingi offers 170+ integrations and AI-assisted landing page building, but lacks any MCP server, public API documentation, SDKs, or webhook support. Without these connection points, you cannot programmatically control or query the tool from Claude, Cursor, or similar agents.
Scored 2026-05-31 by Joonas (TMB).
Landingi MCP & API FAQ
Does Landingi plan to add an MCP server?+
Sources
- Landingi official site: https://landingi.com/
- Pricing source: https://landingi.com/pricing/ (verified 2026-05-31)
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.