原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

agentsocks

作者:Aelethion版本 0.4.0i★ –i在你的电脑上运行
注册名称io.github.Aelethion/agentsocks

安装

概览

作者提供的说明(英文原文)

Claude Code and Codex sessions message each other and share tracked tasks, one machine by default.

PopNx MCP 的三大支柱

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

它能帮你做什么

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

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 其他

安装

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

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 注册中心没有列出需要填写的密钥。

你需要

  • npm已安装 Node.js(用于 npx 命令)

你用的是哪个应用?

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

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

{
  "mcpServers": {
    "agentsocks": {
      "command": "npx",
      "args": [
        "-y",
        "agentsocks",
        "mcp",
        "--host",
        "claude"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add agentsocks -- npx -y agentsocks mcp --host claude

在 Cursor 中打开

或者自己复制设置

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

{
  "mcpServers": {
    "agentsocks": {
      "command": "npx",
      "args": [
        "-y",
        "agentsocks",
        "mcp",
        "--host",
        "claude"
      ]
    }
  }
}

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

在 VS Code 中打开

或者自己复制设置

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

{
  "servers": {
    "agentsocks": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "agentsocks",
        "mcp",
        "--host",
        "claude"
      ]
    }
  }
}

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

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

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

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

它能做什么

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

基础检查i

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

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 Aelethion 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

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

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

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

常见问题

agentsocks 安全吗?

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

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

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

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

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.4.0)于18天前进入注册中心。

哪些应用可以使用它?

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

有什么可以替代它?

同一分类中有:Spec Driven Development, Remote Desktop Commander, dotnet-mcp

替代选择

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

如何看卡片:★ 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昨天更新
安装

dotnet-mcp

作者:Skymly

MCP server for .NET symbols, XAML, source generators, and restricted workspace edit

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

作者的 README

打开 README

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

Your coding agents, talking to each other.

agentsocks lets the Claude Code and Codex sessions on your machine message each other, ask each other questions and hand over tasks. Each message arrives the way that tool already receives one, so nothing is ever typed into a terminal.

Install · See it work · Works with · Limits · Guide

Install

npm install -g agentsocks

agentsocks install agentsocks doctor

Needs Node.js 22.13 or later, Claude Code 2.1.224 or later and Codex CLI 0.162 or later. agentsocks install backs up every file it edits, and --dry-run shows the changes first. New sessions pick it up; sessions already running are not touched.

See it work

Open a Claude Code session and a Codex session. In Codex, type: *tell api-worker the migration is done and the new column is tenant_id.*

Claude Code (api-worker)Codex (codex-web)

| | • Called agentsocks.send_message └ Sent to @api-worker [064c2f] (claude). Delivered. | | › Message from @codex-web (codex): Migration is done; the new column is tenant_id. | | | Claude answers with its built-in SendMessage. | › 📨 agentsocks: new message from a Claude Code session. Read it with read_inbox. • Called agentsocks.read_inbox |

The same works from any shell: agentsocks list shows who is running, and agentsocks send api-worker "the rebase is safe now" sends a message. The guide has every tool and command.

Works with

AgentStatusHears about a messageWakes when idle
Claude CodeSupported, run liveIn its own cross-session inbox, between tool callsYes, as a new turn
Codex CLISupported, run liveThrough its hooks, before the next tool callYes, with codex queue
OpenCodeExperimental, not run live against 0.4A notice on the next tool resultYes
OMP (oh-my-pi)Experimental; an earlier 0.4 build passed a live runA note on the next tool resultYes
HermesExperimental, not run live against 0.4A notice at the start of the next turnOnly with Hermes's API server on
Cursor (CLI and IDE)Experimental, not run live against 0.4A notice after the next tool callNo
GitHub Copilot CLIExperimental, not run live against 0.4A notice after the next tool callNo
Gemini CLIExperimental, not run live against 0.4A notice after the next tool callNo
AiderNot supported: no MCP client and no hooks

Tested with Claude Code 2.1.294 to 2.1.302 and Codex CLI 0.162 to 0.163. Two Claude Code sessions keep using Claude's own SendMessage. How each agent is wired is in the guide.

What you get

  • Messages, questions and tasks. Message any session, ask up to 16 sessions one question and get the answers back together (experimental), or hand over a tracked task with an owner, a state and a result.
  • Nothing typed into a terminal. No tmux send-keys, no pane pastes, no fake user input. A message from another agent is never treated as you, and it can't answer a permission prompt.
  • Attention routing. A busy session isn't interrupted for every message: FYIs come as one digest, and floods wait for the end of its turn (how it decides).
  • Channels and a live view (experimental). Post to a #topic, and watch every session and today's routing in agentsocks top.
  • Beyond this machine (experimental, off by default). An optional gateway links your own machines and your phone over your tailnet (details and limits).

Limits

  • One machine, unless you turn on the gateway or link machines (see Beyond this machine, experimental). Remote Control and cloud sessions are not reached.
  • Codex sessions do not appear in Claude's own ListAgents unless you turn on agentsocks install --claude-listagents (off by default, see More agents); otherwise use list_peers.
  • Aider is not supported: it has no MCP client and no hooks, so there is nothing for agentsocks to hook into.
  • Plain text only.
  • agentsocks builds on Claude Code's cross-session messaging and on Codex CLI's hooks, codex queue and local state. None of these is a stable public API, so a Claude Code or Codex update can stop delivery until agentsocks is updated; agentsocks doctor checks what it can: the Node version, Codex's queue command and each agent's wiring. Tested with Claude Code 2.1.294 to 2.1.302 and Codex CLI 0.162 to 0.163.
  • Not affiliated with or endorsed by Anthropic or OpenAI.
  • Built and tested on Linux. macOS follows Claude Code's own socket-directory rules, and the test suite runs on macOS in CI (the live-agent rehearsals and the tests that need Linux, such as the /proc readers and the gateway source check, run on Linux only), but agentsocks has not been used with real Claude Code and Codex sessions on a Mac, and the typing guard is off there. Termux is best effort: its directories are covered by tests that simulate it, and it is not in CI. Windows named pipes are not supported yet.

The full design, including what was rejected and why, is in docs/SPEC.md.

Docs

  • Guide: how install wires each agent, using it from a shell, routing, tasks, channels, asks, ratings, agentsocks top, delivery states and the gateway.
  • SECURITY.md: what stays on your machine, the threat model and how to report a problem.
  • docs/SPEC.md: the full design, including what was rejected and why.
  • CHANGELOG.md and CONTRIBUTING.md.

Security

Security. Every release, 0.4 included, is reviewed by independent AI reviewers for correctness, security and spec fit, and CI runs the test suite on Linux and macOS (the live-agent rehearsals and the tests that need Linux, such as the /proc readers and the gateway source check, run on Linux only). CI scans the full git history for secrets on every push. See SECURITY.md for what stays on your machine and what does not. *Argo, Aelethion's code security scanner, is coming soon.*

Roadmap

Coming soon:

  • A Grok bot. Reach your sessions from Grok as one more peer, without opening a terminal.
  • MCP outside the terminal. MCP clients that do not run in a terminal, such as desktop and web chat apps, reach agentsocks through a tunnel on your own tailnet carried over the MCP channel, so they no longer need the public listener the ChatGPT and Grok connectors use today.

Related projects

Other people are solving the same problem in different ways. If agentsocks is not the right fit, one of these may be:

  • claude-uds-bridge: a Codex plugin that registers Codex tasks in Claude Code's own session registry, so Claude's built-in ListAgents and SendMessage reach them. Closest to agentsocks in approach. agentsocks adds attention routing, durable tasks and delivery verification.
  • hcom: messaging, watching and spawning across many agent CLIs. It wraps each agent in a terminal and wakes idle ones by typing a trigger into the prompt; agentsocks never types into a terminal.
  • agent-bridge: a Claude Code and Codex bridge using Claude's MCP channel notifications and a proxy in front of the Codex app-server.
  • telepath: a small file-based message bus for Claude Code and Codex, delivered at hook boundaries and through codex queue.
  • codex-claude-bridge: Claude Code and Codex talk through one shared markdown file that each watches.
  • mcp_agent_mail: a mail-style coordination server for any MCP client, with identities, threads and file reservations; agents poll their inboxes.
  • Gas Town: a multi-agent workspace manager with a coordinating agent, workers and a work ledger; it nudges agents through tmux and hooks.

License

MIT

问 PopNx