Codex

Option 1: Synchronity plugin (recommended)

Synchronity ships a Codex plugin in the public marketplace repo themewireco/synchronity (under plugins/synchronity). Add it through Codex's plugin mechanism. Codex reads .codex-plugin/plugin.json and connects to the hosted MCP at https://api.synchronity.app/mcp, and the bundled synchronity-commerce skill means you do not have to say "use Synchronity"; ordinary shopping requests trigger the flow.

The plugin is the same cross-assistant bundle used by Claude Code, so the commerce tools and behavior are identical. If you would rather wire the MCP server directly, use the manual config below.

Option 2: Manual MCP config

Codex CLI speaks MCP, so it connects to Synchronity's hosted MCP server the same way Claude and Cursor do.

Add Synchronity to your Codex MCP config (e.g. ~/.codex/config.toml or the mcp_servers section), pointing at the hosted endpoint:

[mcp_servers.synchronity]
url = "https://api.synchronity.app/mcp"
# Authenticate with your Agent Identity Token (AIT) as a Bearer token:
bearer_token = "YOUR_AIT"

(If your Codex version configures MCP servers via JSON or a different key, use that client's documented MCP-server field; the endpoint + Bearer auth are the same.)

What Codex can do

The same commerce tools as every other client — list stores, browse/search products, build a cart, set shipping, and complete a real checkout with the buyer's approval. Codex receives Synchronity's server instructions on connect, so it knows to invoke the tools when you ask to shop — no need to say "use Synchronity".

Approving a purchase

Checkout + payment require the buyer's explicit approval via a one-time emailed code; Synchronity never completes a purchase without it and only reports success once payment is confirmed.

Caveats

• The hosted endpoint enforces per-AIT rate limits — provision separate agents for separate use cases.