MCP and plugins

Connect supported coding clients to Atoi through an authenticated MCP bridge and a governed first-party plugin pack.

Atoi provides two related client integrations. The MCP bridge exposes authenticated product operations. The governed plugin pack supplies portable instructions that teach a client how to use those operations. Install and verify them separately.

Authorize the bridge

Authorize the CLI before configuring a client:

bash

atoi account login
atoi mcp status --probe --json

The probe checks the authenticated /mcp endpoint and verifies the governed tool contract. The local bridge is started as atoi mcp serve. It translates standard input and output for the client into stateless HTTP requests to Atoi.

The bridge reads the local operator credential at runtime. Generated client configuration does not contain a bearer token. The bridge also fails closed if the server responds with a sessionful or streaming transport that the contract does not support.

Generate client configuration

Print the correct configuration for each supported coding client:

bash

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

Claude Code and Cursor receive JSON-shaped MCP server configuration. Codex receives a TOML mcp_servers.atoi entry. In each case, the configured command is atoi with mcp serve as its arguments.

The command prints configuration; it does not silently edit a client's settings. Place the output in the location managed by that client, then restart or reload the client and run the probe again if the integration does not appear.

Know the governed tools

The first governed client contract exposes three MCP tools:

atoi_projects lists, reads, creates, updates, archives, and restores projects.
atoi_workspace shows, binds, reports, and inspects workspace source truth and changes.
atoi_tasks lists, reads, starts, cancels, continues, inspects, applies, and prepares draft pull requests for tasks.

Task wait behavior is represented by polling the task read operation. The tools operate the same Atoi records used by the product; the plugin does not create a parallel project or task store.

Install the governed plugin pack

The first-party pack is distributed from creative-int/atoi-plugins. Install it through Atoi so the release, commit, manifest, and archive hash are validated and recorded:

bash

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

The pack contains two portable skills: atoi-project-work for operating project work and atoi-proof-review for reviewing task evidence. It carries client manifests for Claude Code, Codex, and Cursor, plus MCP configuration. It does not contain an executable runtime or credentials.

Installed packs can be disabled without removing their receipt:

bash

atoi plugin disable atoi --json
atoi plugin enable atoi --json

Check provenance and drift explicitly:

bash

atoi plugin sync --json

Sync reports lifecycle state; it does not silently replace the pinned pack. Client surfaces read the same governed plugin record, while the CLI owns installation and synchronization.

Diagnose by layer

If tools are missing, first check atoi account status --json, then run the MCP probe. If the bridge is healthy but the client lacks guidance, inspect the plugin receipt and enabled state. If only one client fails, regenerate that client's configuration and compare the command and arguments. This sequence keeps authorization, transport, and portable instructions from being mistaken for one another.