MCP and plugins

The MCP bridge lets a coding client call a small, governed set of Atoi tools. A plugin adds client guidance and keeps a record of what was installed. Set them up separately.

#Check the bridge

atoi account status --json
atoi mcp status --json

The local command is atoi mcp serve. It reads the CLI credential at runtime and forwards each request to Atoi. The credential stays out of client and plugin configuration; Atoi keeps it in macOS Keychain when available and otherwise in a 0600 secrets file.

#Configure a client

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. Put it where the client expects it and reload.

#Call a tool

Open the MCP tools reference for all twelve tool names, argument schemas, result shapes, and runnable 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.

#Install the plugin

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

Install validates the release and records where it came from. sync reports drift; it does not silently update. Disable keeps the record; removal needs --confirm. Use the plugin CLI reference for every subcommand and flag.

#When something fails

1. Check the account identity.
2. Probe the bridge and the tool names.
3. Compare the client's configuration with the printed one.
4. Check the plugin's enabled state.
5. Open the project and task in Atoi.

See Troubleshooting.