agent-intercom

Name: agent-intercom
Author: iambashar

作者：iambashar版本 0.2.5i★ –i在你的电脑上运行

注册名称io.github.iambashar/agent-intercom

安装

概览

作者提供的说明（英文原文）

Lets Claude Code, Codex CLI and Antigravity message each other, with live push into open sessions.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他
你需要填写：AGENT_NAME

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： AGENT_NAME, AGENT_MAIL_DIR

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "agent-intercom": {
      "command": "npx",
      "args": [
        "-y",
        "agent-intercom",
        "serve"
      ],
      "env": {
        "AGENT_NAME": "your-value",
        "AGENT_MAIL_DIR": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add agent-intercom --env AGENT_NAME=your-value --env AGENT_MAIL_DIR=your-value -- npx -y agent-intercom serve

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "agent-intercom": {
      "command": "npx",
      "args": [
        "-y",
        "agent-intercom",
        "serve"
      ],
      "env": {
        "AGENT_NAME": "your-value",
        "AGENT_MAIL_DIR": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "agent-intercom": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "agent-intercom",
        "serve"
      ],
      "env": {
        "AGENT_NAME": "your-value",
        "AGENT_MAIL_DIR": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

AGENT_NAME 必填 env
This agent's mailbox name, e.g. claude, codex or gemini
AGENT_MAIL_DIR env
Mailbox folder shared by all agents (default ~/.agent-mail)

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 iambashar 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32655 个服务器的 0%
发布到注册中心的时间比此分类中其他 32655 个服务器的 66% 更新
基础检查结果等于或优于此分类中其他 32655 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

agent-intercom 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：AGENT_NAME

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.2.5）于19天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, SuperCollider

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211前天更新

安装

SuperCollider

作者：Tok

Make sound with SuperCollider: synths, drums, chords, melodies and soundscapes over OSC.

在你的电脑上运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

-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

Get started

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.ts and 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 gemini CLI no longer accepts personal Google AI Pro sign-ins; Google moved those users to the Antigravity CLI (agy). Its agent is named gemini here by default.

See it work

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.

What you get

Supported agents

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

How push works

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")

Delivered once. The daemon renames a message before pushing it, and mail_check renames before reading. Whoever wins the rename delivers it.
Fails safe. A failed push puts the file back in the inbox and retries after 30 s. If no session is open, the message waits for mail_check.
Addressing. Pick a session with 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

Claude Code: docs/claude-monitor.md. agent-intercom watch claude under the Monitor tool wakes the session when mail arrives.
Codex: docs/codex-listen.md. A listener prompt that loops on mail_check(wait_seconds=300).

Across machines

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.

More than one session per CLI

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

CLI

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

Security

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.

Treat inbox contents as untrusted text. Don't

只显示了开头部分；其余内容请在仓库中阅读