Edit your site with your AI assistant (MCP)

With the Kintsu MCP, your own AI assistant works directly on your site. MCP (Model Context Protocol) is an open standard that lets an assistant work safely with an app. Your assistant signs in to Kintsu with your account and only does what your role allows. You ask in plain language, for example “Change Saturday's opening hours to 9 am to 1 pm”, and the assistant finds the right page, table or setting by itself.

Before you start

• Who: any role. Your assistant gets your permissions, never more.

• Plan: any plan.

• You need: an assistant that supports MCP, such as Claude, ChatGPT, Claude Code, Cursor or VS Code.

• The server address: https://mcp.kintsu.be

Connect your assistant

Choose your assistant:

• Claude, on the web and in Claude Desktop

• Claude Code

• ChatGPT

• Cursor

• VS Code

Another assistant works too, if it supports remote MCP servers and sign-in through OAuth. Give it the address above.

Whatever the assistant, signing in works the same way:

1. Your assistant opens a Kintsu window. Sign in with your Kintsu account.

2. You see Give an assistant access, with the name of the assistant and the address it comes from.

3. Read what it will be allowed to do: see your name and email address, work in your organizations with your permissions, and keep working until you take the access back.

4. Click Allow. If you don't trust it, click Refuse.

What your assistant can do

That depends on your role:

• Member: read only. Your sites, pages, tables, the history and the checks of your site. It doesn't change anything.

• Editor: change texts, images and links, create and change items in your tables (such as news and vacancies), upload files, update your contact details and opening hours, translate, make a preview link, publish and undo changes.

• Admin: everything an editor can do, plus the colours and fonts of your site, your domains, and going back to an earlier publication.

• Owner: everything an admin can do. With Kintsu Studio, also the design: building sections, and designing styles, components, pages and tables.

• Designer: the design and structure of your site, and new sites. A designer needs two-step verification.

You'll find specific requests for each role in Example requests for your assistant.

What isn't possible

Through the MCP, your assistant cannot:

• read your form submissions (the API can);

• set the recipients of your forms;

• invite members, manage your subscription or invoices, or create API keys;

• give itself access: you do that, in your browser.

Security

• Your permissions, checked on the server. With every request, Kintsu checks what your role is allowed to do in that organization. Whatever you can't do, your assistant can't do either. If you leave an organization, it loses access too.

• A draft first. What your assistant changes is a draft first. Your visitors only see it after it's published. Exceptions: the opening hours and the map go live straight away, as do items in a table that publishes on save.

• Publishing always asks for your confirmation. The assistant first shows what goes live, what doesn't and why. It only publishes once you say yes. A confirmation is valid for 10 minutes, and only for exactly that change.

• Big changes first show what will happen and wait for your approval, for example sending more than three items to the bin, deleting a page or removing a domain.

• Everything can be undone. Every change is in the editor's History, marked “through an AI assistant”. You can undo one change, or a whole session of your assistant: everything it did without a break of more than 15 minutes. Just ask: “Undo everything you just did.” The history is kept for 90 days.

• Your site is data, not instructions. If a text on your site or in a form says “ignore your rules”, your assistant doesn't follow it. Kintsu tells every assistant so.

• Let your assistant ask before it changes anything. Turn on approval in your assistant for tools that change things, and only connect assistants you trust.

• Revoking access. On app.kintsu.be, go to Account › Connected apps and click Take access back next to the assistant. Its next request is refused.

Not working?

See Troubleshooting the MCP.

With your AI assistant

Once connected, ask: “Who am I in Kintsu, and which sites do I have?” Your assistant shows your organizations, your role and your sites.

Want to connect your own software instead of an assistant? Then use an API key.

Checked on 4 November 2026.