Does Landingi have an MCP server?

Landingi is building an MCP server (Orbit), but it is not live yet. So the honest read for anyone wiring an agent today: there is no Landingi MCP endpoint you can connect to right now. Orbit is announced on landingi.com/product/orbit as the bridge that will link Landingi to your preferred LLM, and the AI vision behind it is real, but it sits in development rather than shipping.

What Orbit aims to connect is the interesting part. Landingi already runs two AI features: Lunar, the AI page generator that builds landing pages from a prompt, and Solis, the AI insights layer that reads performance data. Orbit is pitched as the connective tissue that hands those plus the wider platform to an LLM, so an agent could spin up and manage pages without leaving the chat. That is the destination Landingi is steering toward, not a feature you can call this week.

Until Orbit ships, the live integration path is the REST API at api.landingi.com/v2, backed by Zapier and Make for no-code automation. If you want an agent touching Landingi today, you point it at the API and wrap the calls yourself. I will move Landingi up the MCP-readiness scale the moment Orbit has a documented, connectable endpoint.

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.

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.

Not agent-ready. Landingi has no MCP, no documented API, and no LLM integrations, making it inaccessible to Claude or Cursor workflows. The 170+ integrations are traditional webhooks and tools, not agent-capable connections.

Scored 2026-06-07 by Joonas (TMB).

Landingi: No MCP yet