Connect Claude, Cursor or VS Code to CMS Orbit

An AI assistant that can read your website's content can do useful work: draft a new page, tighten search descriptions, adapt a page for another country or find every page that still mentions last year's offer. CMS Orbit makes this possible with MCP, the Model Context Protocol, an open standard that assistants such as Claude, Cursor and VS Code use to work with other systems.

This guide connects an assistant to CMS Orbit in a few minutes, and explains what it can and can't do once it's in.

Before you start: switch agents on

Open Configuration › AI agents on the website the assistant should work on. Three switches decide what's allowed:

• Allow AI agents in the organisation: On by default. Turning it off stops every agent on every website at once.
• Allow AI agents on this website: Off until an Administrator turns it on, so nothing connects by accident.
• Allow drafts in production: Off by default. Agents can then read Production but only draft in environments such as Staging.

An agent always acts for a person, and never gets more rights than that person has. If you can't edit a page, neither can your assistant.

Sign in, or use a key

There are two ways to connect, and both act for you:

• Sign in: The assistant opens a browser, you sign in to Bifröst Orbit as you always do, choose the website and select Allow. This suits Claude, Claude Code, Cursor and VS Code, and the connection renews itself as long as it's used at least once every 30 days.
• Agent key: A key starting with cms_ag_, for clients that can't sign in, scripts and scheduled jobs. It lasts 7, 30 or 90 days, or a year, and can be limited to certain regions.

Connect your assistant

The quickest way is on the AI agents screen itself. Add to Cursor and Add to VS Code open the app and add the server for you, and Copy Claude Code command copies the command for a terminal. Each uses the address of the CMS you're in, so it works the same on staging.

Claude

In Claude's connector settings, add a custom connector with the address https://app.bifrostorbit.com/cms/mcp. Claude opens the sign-in page; sign in, choose the website and select Allow.

Claude Code

Run claude mcp add --transport http cms-orbit https://app.bifrostorbit.com/cms/mcp, then run /mcp inside Claude Code and choose the server to sign in.

Cursor and VS Code

Use the buttons on the AI agents screen, or add the same address to the app's MCP settings by hand. Both ask you to sign in when they first connect.

Check that it works

Ask something that only reads, such as "List the scopes you can work in" or "Find the page at /products/hiking-boots". The assistant should answer with the environments, regions and languages it can see, or with the page. Tools work in Staging unless you name another environment, and in the default region and language unless you ask for others.

What an agent can and can't do

An agent drafts; people decide. Everything it writes is marked as drafted by AI and waits for a person to review and publish it. It has no tools at all for publishing, scheduling, deleting other people's work, or changing protected prices, people, roles, settings or schemas. Each connection may make 60 requests a minute, and every change it makes appears in the page's history with the agent's name. Read more about this in AI agents in your CMS, with a person in control.

Switch it off again

On the AI agents screen, open the menu on a key or signed-in connection and choose Revoke; the agent is refused from its next request. To stop every agent at once, turn off Allow AI agents on this website. And if the person an agent acts for leaves the organisation, all their keys and connections stop working.

Try it

The full steps, including keys for scripts and every error you might see, are in Connect an AI agent over MCP. Start a 14-day free trial, connect your assistant and ask it to draft your next page.