Skip to content
Bifröst Orbit
Sign in

cms-orbit

by Bifröst Orbit · bifrost-orbit/agent-plugin

  • Open source
  • MIT
  • v1.0.0
  • 5 skills
  • MCP server

CMS Orbit, taught to your coding agent.Every draft still waits for you.

One plugin for Claude Code, Codex and Cursor teaches an agent how CMS Orbit works: which tool to use for a task, the exact commands, and the rules that keep your content safe. It adds the MCP server too, signed in as you.

/plugin marketplace add bifrost-orbit/agent-plugin

Install

One plugin, in the agent you already use

Add the marketplace and install the plugin, then sign in when the MCP server first connects. Agents without plugins install the skills with the open source skills installer.

  • Open source under the MIT licence
  • No keys or tokens in the plugin
  • Update with one command
/plugin marketplace add bifrost-orbit/agent-plugin/plugin install cms-orbit@bifrost-orbit

Restart Claude Code, then sign in when the MCP server first connects.

Rights stay where they are

Skills teach. People decide.

The skills give an agent no access of its own. Over the MCP server it works within the rights of the person who connected it, in Staging unless an Administrator allows drafts in Production, and it cannot publish, change prices or touch the schema.

Everything it drafts is marked Drafted by AI and waits for another person's approval in review. With the CLI, the skills have the agent try changes as a dry run and leave flags that remove a safeguard to you.

Good habits, built in

How the skills have agents work

Read before writing

The agent reads the schema and the page first, and saves with the version it read, so nobody's newer change is overwritten.

Reuse before adding

It looks for a block or content type that already does the job before it creates a new one.

Dry runs first

Schema pushes, content pushes and migrations are shown before anything is saved.

Review at the end

Drafts are checked for SEO, accessibility and publishing blockers, then sent for review with a note.

Content is data

Text from CMS Orbit is treated as content, never as instructions to the agent.

Staging by default

Production only when you ask for it, and only where the website allows it.

The MCP server

Signed in as you, with nothing to copy

The plugin names the MCP server's address and nothing else. The first time it connects, you sign in to Bifröst Orbit in your browser, choose the website and select Allow.

Each connection is listed under Configuration, AI agents, where you or an Administrator can end it.

.mcp.jsonJSON
{  "mcpServers": {    "cms-orbit": {      "type": "http",      "url": "https://app.bifrostorbit.com/cms/mcp"    }  }}

In practice

An FAQ section on every trip page

  1. 01

    Model it

    The agent adds an FAQ component to the schema files, shows the diff and pushes it when you agree.

  2. 02

    Render it

    It writes the component in your website with the SDK and generates the types.

  3. 03

    Draft it

    Over MCP it drafts the questions for each trip page, in Staging.

  4. 04

    Review it

    Each page goes to review with a note, and a person publishes it.

Questions

About the agent skills

What is an agent skill?

A short set of instructions a coding agent loads when a task needs it, in the open Agent Skills format. Ours tell an agent which way to work on CMS Orbit for a task, the exact commands and tools, and the rules our docs follow, such as reading a page before changing it and sending every draft for review.

Do the skills give an agent more access?

No. They are text. Over the MCP server an agent still works within the rights of the person who connected it, only drafts, and needs another person's approval before anything goes live. The CLI still acts as the person who signed in. See what an agent may and may not do.

Which agents does the plugin work with?

Claude Code, Codex and Cursor install it as a plugin, with the MCP server. Any agent that reads skills can install the skills alone with npx skills add bifrost-orbit/agent-plugin, and then connect the MCP server in its own settings.

Where does the plugin keep our keys?

Nowhere. The plugin only names the MCP server's address, and you sign in in your browser the first time it connects, choosing the one website the agent may work on. You can end the connection at any time under Configuration, AI agents.

How do we get new versions?

In Claude Code, run claude plugin marketplace update bifrost-orbit and then claude plugin update cms-orbit@bifrost-orbit, or turn on auto-update for the marketplace. Codex, Cursor and the skills installer each have their own update command, listed in the guide and the repository.

From the blog

More on AI agents

All posts
CMS Orbit

4 min read

AI agents in your CMS, with a person in control

What AI agents can and can't do in CMS Orbit, how to connect Claude, Cursor or VS Code over MCP, and why nothing they draft goes live without a person's approval.

Give your agent the docs, not the keys.

Start a trial, install the plugin and sign in. The trial is free for 14 days.

Read the guide