vstratful

Agent Bridge MCP — Communication skill for Claude Code

Communication community

Local MCP messaging between Claude Code and Codex sessions on the same machine.

How to install Agent Bridge MCP

This entry records only its repository, not the path inside it, so there is no exact command to give. Open vstratful/agent-bridge-mcp and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Agent Bridge MCP does

Local MCP messaging between Claude Code and Codex sessions on the same machine.

Alternatives in Communication

  • HolaOS — Open-source agentic workspace enterprises can make their own 10.9k ★
  • Lark Coding Agent Bridge — Bot that bridges Feishu/Lark messenger with a local Claude Code or Codex CLI 2.4k ★
  • Pokegents — Pokegents is a local, Pokémon-inspired dashboard that turns Claude Code and Codex sessions into a local team d 95 ★

README

agent-bridge-mcp

Discover and exchange text between your existing Claude Code and Codex sessions. The bridge uses your installed, authenticated clients; it needs no API keys and makes no model API calls. Messages can start work and consume client usage.

Requirements

Linux or WSL 2, Node.js 24+, Claude Code >= 2.1.224, and Codex with its app-server daemon running. Tested with Claude Code 2.1.312 and Codex CLI 0.165.0.

The bridge depends on undocumented Claude and Codex internals and may break on client updates. Run `agent-bridge-mcp doctor` first when something stops working.

Install and connect

Install from GitHub; no account or SSH key is needed.

npm pack git+https://github.com/vstratful/agent-bridge-mcp.git
npm install -g ./agent-bridge-mcp-*.tgz && rm ./agent-bridge-mcp-*.tgz

Don't use `npm install -g git+https://…` directly: npm's global git install fails to build the package (`tsc: not found`). Packing first builds it in a normal clone.

Register in both clients using absolute paths:

claude mcp add --scope user --transport stdio agent-bridge -- "$(command -v node)" "$(npm root -g)/agent-bridge-mcp/dist/cli.js" serve
codex mcp add agent-bridge -- "$(command -v node)" "$(npm root -g)/agent-bridge-mcp/dist/cli.js" serve

Version managers can give a client a different, older Node; absolute paths keep both clients on the Node version used to install the bridge. Reconnect their MCP connections (`/mcp`) after registration or updates. Installation sends no messages. The bridge must run in the same host process namespace as the sessions.

agent-bridge-mcp doctor

Doctor reports PASS, WARN, FAIL or SKIPPED and fixes for non-passing checks; any FAIL exits with status 1. It checks metadata and configuration without sending messages or creating bridge files. Unsupported registration queries are SKIPPED and do not affect the exit code.

Using it

You don't call the bridge yourself. Talk to Claude or Codex as you normally woul