MCP and plugins

Install the Atoi plugin in Claude Code, Codex, or Cursor, and give that client governed access to your work through the Atoi CLI

Open in Atoi

The credential stays on your machine, out of client and plugin configuration.

The Atoi plugin brings Atoi into the coding client you already use. It adds one skill, atoi, that teaches the client how to work in Atoi. It also starts the CLI's MCP bridge, atoi mcp serve, which gives the client Atoi's governed tools with your own account's authority.

No token goes into the plugin or the client's configuration. The bridge reads your credential from the CLI at runtime.

#Before you install

Install the terminal from Terminal, then sign in once:

atoi account login
atoi account status --json

atoi account login opens a browser with a device code. It is not atoi login, which pairs a Computer. Until you sign in, the client lists the Atoi server but cannot connect to it, because the bridge stops with Atoi operator login required.

#Install the plugin

/plugin marketplace add creative-int/atoi-plugins
/plugin install atoi@atoi

codex plugin marketplace add creative-int/atoi-plugins
codex plugin add atoi@atoi

git clone https://github.com/creative-int/atoi-plugins.git
cursor-agent --plugin-dir ./atoi-plugins/plugins/atoi

In Claude Code, the same two steps from a shell are claude plugin marketplace add creative-int/atoi-plugins and claude plugin install atoi@atoi. claude mcp list then shows plugin:atoi:atoi running atoi mcp serve.

In Codex, the first command adds the catalog and the second installs from it, so the plugin is not installed until both have run. codex mcp list then shows atoi, and a new Codex session loads the skill.

Cursor reads the directory as an Agent Plugin. It registers the Atoi server and makes /atoi available.

Each path above was installed from a fresh clone of the public repository on 2026-09-16. The receipts are in atoi-plugins/docs/proofs/install.

#What the plugin contains

The plugin is plugins/atoi in creative-int/atoi-plugins, laid out to the Agent Plugins 1.0.0 standard.

Path	What it holds
`plugin.json`	The plugin's name, version, and description
`mcp.json`	One MCP server, `atoi mcp serve` over stdio
`skills/atoi`	The `atoi` skill and its two references

The skill teaches the order of work: read before you write, find a Workspace's thread, run tasks under a safety profile, and confirm every consequential step. Its tool table is generated from the tools Atoi ships.

#Configure a client by hand

Skip the plugin and add only the bridge:

atoi mcp config --client codex
atoi mcp config --client claude-code
atoi mcp config --client cursor
atoi mcp config --client pi

For Codex, the output is:

[mcp_servers.atoi]
command = "atoi"
args = ["mcp", "serve"]

The command prints configuration. It never edits your client. Codex reads ~/.codex/config.toml. Cursor reads .cursor/mcp.json in a project or ~/.cursor/mcp.json for every project, and expects "type": "stdio" on the entry. Claude Code reads .mcp.json at the project root. Reload the client after you save.

#Call a tool

The MCP tools reference lists every tool Atoi ships, with argument schemas, result shapes, and call and response examples. The tools act on the same records as the apps. A prepare or apply receipt describes what happened in Atoi, not in your local checkout.

#The plugin's skills in Atoi

atoi plugin install creative-int/atoi-plugins --json
atoi plugin list --json
atoi plugin view atoi --json
atoi plugin sync --json

This is separate from installing the plugin in a client. atoi plugin install adds the plugin's skills to your Atoi Skills from the release the CLI pins, and records where they came from. sync reports drift. It does not silently update. Disable keeps the record, and removal needs --confirm. Use the plugin CLI reference for every subcommand and flag.

#Not available yet

ChatGPT and Claude.ai reach MCP servers from their own clouds, so they need Atoi's hosted connection with sign-in. That connection is not available yet. Until its checks pass, the plugin keeps using the local bridge. The checks are in atoi-plugins/docs/proofs/door.

Cursor also offers cursor-agent plugin marketplace add. It has not been tried with this plugin, because trying it adds a marketplace to a person's own Cursor account, so this page does not describe it yet.

#When something fails

Run atoi account status --json, and atoi account login if it is not connected
Check that the client lists the Atoi server: claude mcp list or codex mcp list
Compare the client's configuration with the printed one
Check that the plugin is enabled in the client
Open the project and task in Atoi

Read Troubleshooting when none of those five steps clears the problem.

Was this useful?