Working with an AI agent

An AI assistant such as Claude can read and edit the site's pages for you. It works through the same editor you use, signed in as you, so it can do what you can do and is held to the same rules.

The assistant connects to the site through MCP (the Model Context Protocol), which most AI assistants support.

Setting it up

Your site's team gives you its MCP address, which ends in /mcp. You add it to your assistant once.

• Claude (on the web or the desktop app): in Settings, open Connectors, choose Add custom connector, and paste the address. Your plan must allow custom connectors.
• Claude Code: run this, with your site's address:

• Another assistant: add the address wherever it lets you add an MCP server or connector that is reached by URL.

The first time the assistant uses it, your browser opens the site's sign-in. Sign in as you always do, then choose Allow on the page that asks whether to connect the assistant. From then on the assistant works as you, until you sign out or the sign-in runs out, when it asks you again.

Running it on your own computer

A developer can run the MCP server locally instead of using a hosted one. From an Inka checkout with its dependencies installed, add it to the assistant with the address of the site's editor:

The first call opens your browser to sign in, as above. The sign-in is kept in ~/.config/inka-mcp/tokens.json, readable only by you, so you aren't asked again until it runs out.

What the assistant can do

• Find pages by their text, and list what is in a section.
• Read a page, and see it as a visitor sees it.
• Add, change, move and remove blocks, and change a page's own fields such as its title and summary.
• Preview a change as a visitor would see it before saving it.
• Add, move, rename and delete pages.
• Change a template's locked blocks on every page that uses it, but only when you ask for that.

It learns what each kind of block is for from the site itself: the description and guidance the site's developers gave it, examples of it, and pages that already use it.

What you can ask it

Ask in your own words, naming pages by their title or where they are on the site. Some examples:

• Find things: "Which pages mention our opening hours?" or "List the pages in the News section that are still private."
• Read and check: "Read the About page and tell me what's out of date." or "Show me the Pricing page as a visitor sees it."
• Change a page: "On the Contact page, add a tip after the first paragraph saying we reply within two days."
• Rework a page: "Rewrite the summary of the Events page to under 30 words, and put the opening hours in a table."
• Try a layout: "Show me two ways to lay out the Services page with what's on it now, then build the one I choose."
• Make a page: "Create a page in News called 'Spring opening', with a heading, a short introduction and a link to the Events page."
• Tidy the site: "Move the old Press page into the About section and rename it 'Media'."
• Learn the blocks: "Which block should I use for a list of steps? Show me an example of it."
• Change a template: "Change the footer's copyright line on every page." It changes a template's locked blocks only when you ask, and says which templates it changed; every page using them changes too.

A few things help:

• Ask it to show you a change before it saves. Its preview is drawn by the site itself, as visitors would see it.
• Say what not to touch, such as "leave the headings as they are".
• It can't publish. Publish its pages yourself, through your site's usual workflow.

The same rules as you

• Your permissions. It can see and change only what your account can.
• The editor's checks. It can't put a block where the editor wouldn't let you, change a template's locked blocks without your say-so, or save a page the editor would refuse.
• Your name. What it saves is saved as you, like your own edits.

Ask it to show you a change before it saves. A preview is saved nowhere, and nothing on the site changes until the assistant saves.