Codex Peers MCP
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Codex Peers MCPfind other active sessions working on this repository"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
codex-peers-mcp
Peer discovery + messaging for Codex sessions on one machine.
Isolation tip: on shared hosts, set a unique
CODEX_PEERS_NAMESPACE(and optionallyCODEX_PEERS_TOKEN) to prevent cross-user message mixing.
Features
whoami: get current peer id/contextlist_peers: find other Codex sessions (machine,directory,reposcopes)send_message: direct message by peer idsend_message_by_filter: message a peer byrepo_name/cwd_contains/summary_containsset_summary: publish what this session is working oncheck_messages: read unread inbox
Architecture
Local broker daemon on
localhost:${CODEX_PEERS_PORT:-7899}SQLite backing store (
${CODEX_PEERS_DB:-~/.codex-peers.db})MCP stdio server per Codex session
Install
cd ~/clawd/projects/codex-peers-mcp
bun installRun broker manually (optional)
bun run src/broker.tsThe MCP server auto-starts the broker if it is not running.
Register with Codex MCP
Add this server to Codex MCP config (example command shape; adapt to your codex mcp add flow):
codex mcp add codex-peers -- bun ~/clawd/projects/codex-peers-mcp/src/server.tsTest quickly
Option A — one-command smoke test (recommended for new users)
cd ~/clawd/projects/codex-peers-mcp
bash scripts/smoke.shThis runs a self-loop MCP validation in Codex:
whoamiset_summarysend_message(to self)check_messages
You should see JSON output followed by smoke: PASS.
Option B — manual two-session test
Start Codex session A and B with this MCP server enabled.
In B: call
set_summary(e.g.receiver-smoke).In A: call
send_message_by_filterwithsummary_contains=receiver-smoke.In B: call
check_messages.
CLI
bun run src/cli.ts status
bun run src/cli.ts peers
bun run src/cli.ts send <peer_id> "hello"Auth caveat (important)
If Codex says quota exceeded unexpectedly, verify auth mode:
codex login statusIf it says API key mode, switch back to ChatGPT OAuth for this workflow:
codex logout
unset OPENAI_API_KEY
codex loginEnv vars
CODEX_PEERS_PORT(default7899)CODEX_PEERS_DB(default~/.codex-peers.db)CODEX_PEERS_NAMESPACE(defaultdefault) — use a unique namespace to isolate teams/users on shared hostsCODEX_PEERS_TOKEN(optional) — when set, broker requiresx-codex-peers-tokenon non-health routesCODEX_PEER_ID(optional override for generated peer id)
Validation scripts
bash scripts/test-broker-routes.sh
bash scripts/smoke.shThis server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jscianna/codex-peers-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server