Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Lets Claude Code, Codex CLI and Antigravity message each other, with live push into open sessions.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
AGENT_NAME, AGENT_MAIL_DIRYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"agent-intercom": {
"command": "npx",
"args": [
"-y",
"agent-intercom",
"serve"
],
"env": {
"AGENT_NAME": "your-value",
"AGENT_MAIL_DIR": "your-value"
}
}
}
}Run this in your terminal
claude mcp add agent-intercom --env AGENT_NAME=your-value --env AGENT_MAIL_DIR=your-value -- npx -y agent-intercom serveFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"agent-intercom": {
"command": "npx",
"args": [
"-y",
"agent-intercom",
"serve"
],
"env": {
"AGENT_NAME": "your-value",
"AGENT_MAIL_DIR": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"agent-intercom": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"agent-intercom",
"serve"
],
"env": {
"AGENT_NAME": "your-value",
"AGENT_MAIL_DIR": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
AGENT_MAIL_DIR envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account iambashar, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: AGENT_NAME
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.5) reached the registry 19 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Draugr
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Security scanning for AI agents: SAST, SCA, secrets, IaC, DAST, ranked by real risk.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
-supported-7B8CFF?style=flat-square)
Let Claude Code, Codex CLI and Antigravity (Gemini) message each other,
and land each message straight in the other agent's open session.
If it saves you time, a ⭐ helps other people find it.
Get started · See it work · How push works · Across machines · CLI · Security · Contributing
npx agent-intercom install
Using Claude Code only? Install it as a plugin instead:
/plugin install agent-intercom --marketplace iambashar/agent-intercom
On Claude Code older than 2.1.275: /plugin marketplace add iambashar/agent-intercom , then /plugin install agent-intercom@agent-intercom . The plugin also adds a skill that teaches Claude the mailbox conventions.
The npx command registers the MCP server with every CLI it finds. Restart them, and each agent gets three tools: mail_send, mail_check and mail_peers. Then ask in plain words:
You → Claude: Ask codex to review the diff in
src/parser.tsand wait for its answer.
Turn on live push so nobody has to poll. Install it globally, because the daemon needs a stable path:
npm i -g agent-intercom
agent-intercom install --push
What install changes, per CLI
| CLI | Registration | Extra for push |
|---|---|---|
| Claude Code | claude mcp add, user scope | nothing; uses Claude Code's peer socket |
| Codex CLI | a managed block in ~/.codex/config.toml (backed up first) | nothing; uses the Codex app-server daemon |
| Antigravity (`agy`) | agy mcp add | a session hook in ~/.gemini/config/hooks.json |
Use --only claude|codex|gemini for one CLI, and --local to pin a git checkout instead of npx. agent-intercom uninstall removes all of it, including the push daemon.
[!NOTE]
The old
geminiCLI no longer accepts personal Google AI Pro sign-ins; Google moved those users to the Antigravity CLI (agy). Its agent is namedgeminihere by default.
Neither agent polls. The request appears in Codex as a new turn the moment it is sent, and the reply lands in Claude the same way.
| Agent | Mailbox name | How a message reaches the open session |
|---|---|---|
claude | Claude Code's local peer-messaging socket, the channel SendMessage uses between sessions. Arrives labelled as from another session. | |
codex | The shared app-server daemon the Codex TUI runs on: turn/start, or turn/steer when a turn is already running. | |
gemini | agy agentapi send-message into the conversation. Each session registers itself once through a hook. | |
| Any other MCP client | anything | No push. It reads with mail_check, or blocks with mail_check(wait_seconds=300). |
| Tool | What it does |
|---|---|
mail_send(to, body, reply_to?) | Drop a message in another agent's inbox |
mail_check(wait_seconds?) | Read and consume your messages; with wait_seconds (max 300) it blocks until one arrives |
mail_peers() | List known agents |
sequenceDiagram
autonumber participant C as Claude Code participant M as ~/.agent-mail/codex/inbox participant P as pushd participant X as Codex CLI (open session) C->>M: mail_send(to: "codex", body) M-->>P: file appears (fs.watch, no polling) P->>M: claim: rename to .json.pushing P->>X: turn/start with the message X-->>P: turn accepted P->>M: move to read/ Note over X: Codex works on it, then replies with mail_send(to: "claude")
mail_check renames before reading. Whoever wins the rename delivers it.mail_check.claude. , codex. or gemini. . Otherwise the most recently active session gets it, or the one named in ~/.agent-mail/routes.json: { "claude": "api-server", "codex": "019f018a" }
[!WARNING]
Push relies on undocumented internals of all three CLIs, and an update can change them without notice. When that happens, pushes fail, get logged, and the mail falls back to the inbox. Protocol details: docs/live-push.md.
Without the push daemon
agent-intercom watch claude under the Monitor tool wakes the session when mail arrives.mail_check(wait_seconds=300).Agents on a machine with no shared filesystem, such as a GPU server or an HPC cluster, join over SSH with bridge.sh. It moves each message to the machine its recipient lives on, and pulled mail is pushed like any other.
BRIDGE_HOST=gpu-box REMOTE_AGENTS="claude-gpu" ./bridge.sh
flowchart LR
subgraph laptop["💻 Laptop"] A[claude] & B[codex] & G[gemini] end subgraph gpu["🖥️ gpu-box"] R[claude-gpu] end laptop <-- "bridge.sh · rsync over SSH" --> gpu
More: docs/remote-bridge.md.
Names are just AGENT_NAME. Give each session its own, for example claude-api and claude-web:
npx agent-intercom install --only claude --claude-name claude-api
agent-intercom install [--only claude|codex|gemini] [--claude-name N] [--codex-name N] [--gemini-name N] [--local] [--push]
agent-intercom uninstall MCP entries, agy hook and push daemon agent-intercom push install push daemon as a login service (launchd / systemd --user) agent-intercom push uninstall agent-intercom push run push daemon in the foreground agent-intercom status unread/read counts per agent agent-intercom watch one line per new message, without consuming it agent-intercom serve the MCP server on stdio
This is a local mailbox with no authentication. Any process running as you can write to ~/.agent-mail/*/inbox, and an agent treats a message as input to act on. With push on, that input reaches your open sessions without you typing anything.
Only the beginning is shown; read the rest in the repo