Definition
In depth
MCP (Model Context Protocol) is how Cursor, Claude, and other coding agents call platform tools instead of inventing a shadow CMS in the chat. On LUNO, MCP shares the same system of record as Console and the public API.
The package is `@luno-cms/mcp`. Run `npx -y @luno-cms/mcp setup`. The CLI opens the browser so you confirm the connection. Do not paste an API key into chat. That is the whole security posture of setup.
What agents can do depends on the key. Prefer a full key for day-to-day modeling and publish. Use a content-only key when the loop should not touch schema. Revoke when the agent or the machine changes.
MCP is not a website generator. The agent still writes the frontend you asked for. LUNO is the backend the agent operates — content, forms, and publish — so the generated UI has somewhere real to land.
If a CMS only offers community plugins for agents, treat that as a bolt-on. First-class MCP means the same models, the same publish state, and the same audit trail the human dashboard already uses.
More
More terms
- Agent API key →
Scoped credentials for agents (content vs schema) so automation cannot delete control-plane primitives by accident.
- Backend platform for apps and agents →
A backend that treats coding agents as first-class operators alongside humans — same record, different surfaces.
- AI-era Backend Platform →
The category for a durable backend humans and agents share — because app code got cheap, but backend ownership did not.
- Never build backends again →
- Hosted Backend Platform →
- Seat tax (CMS pricing) →
- Production governance →
See it in the product
Check Capabilities and Developers to see definitions become implementation.