MCP for AI agents

AI assistants are starting to draft and update content. Given raw access to a CMS, an assistant can produce layouts your design system doesn't allow, skip a required field, or change content nobody asked it to. Inka's Model Context Protocol (MCP) server gives assistants the same way in as people, and nothing more.

• Signed in as a person. Someone connects their assistant by signing in to the site as they always do and allowing it. The assistant can then do what that person can do, and nothing they can't.
• Only what your design system allows. The assistant is offered only the blocks and fields that are valid where it is working, from the same block schemas your editors use. It can't place a block where the editor wouldn't, or save a page the editor would refuse.
• The same advice editors get. For each kind of block, it has the description and guidance your front end gives it, examples of the block filled in, and a page on the site that already uses it.
• It sees the page, not just the data. It can look at a page as visitors see it, and render a change or a whole new layout before saving anything, so it can judge layout and visual impact, not only the words.
• Read, preview, save. It reads the page it will change, previews the result, and only then saves. Text it writes is markdown; Inka turns it into the rich text your blocks hold.
• Templates stay put. A template's locked blocks change only when the person asks for that, and then on every page that uses the template, just as when an editor does it.
• The same record. What it saves is saved as the person who connected it. It has no way to publish: its pages go through your usual workflow. Its edits to a page that is already published are live, like an editor's, so ask it to preview first.

The MCP server runs alongside the Inka editor, as a service of its own. How to connect an assistant, and what it can do, is in the editor guide.

Try it on the demo

Connect your assistant to this site's MCP server, sign in with the demo account, and ask it to change a page. Nothing you or it do on the demo is kept.

First, add the MCP server to your assistant as a custom connector (or MCP server), with the address https://inkasite-mcp.fly.dev/mcp. In Claude Code:

When your assistant first uses it, your browser opens the editor's sign-in. Choose the demo sign-in, then Allow to let the assistant work as the demo account.

Then ask it for something on the site, for example: "Add a tip to the Pricing page saying the first month is free, and show me before you save."