Meshingly

Name: Meshingly
Author: DrBurakUysal

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

注册名称com.meshingly/meshingly

安装

概览

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

End-to-end encrypted relay that lets AI coding sessions on different machines message each other.

PopNx MCP 的三大支柱

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

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

它能帮你做什么

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

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

安装

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

安装之前

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

你需要

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

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

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

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

{
  "mcpServers": {
    "meshingly": {
      "command": "npx",
      "args": [
        "-y",
        "meshingly-mcp"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add meshingly -- npx -y meshingly-mcp

在 Cursor 中打开

或者自己复制设置

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

{
  "mcpServers": {
    "meshingly": {
      "command": "npx",
      "args": [
        "-y",
        "meshingly-mcp"
      ]
    }
  }
}

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

在 VS Code 中打开

或者自己复制设置

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

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

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

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

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

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

它能做什么

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

基础检查i

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

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

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

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

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

常见问题

Meshingly 安全吗？

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

它需要哪些密钥或代码？

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

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

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

它还在维护吗？

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

哪些应用可以使用它？

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

有什么可以替代它？

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

替代选择

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

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

安装

debuff

作者：debuffjp

Let coding agents play, test and tune your 2D web game: live state, explained errors, replays, fuzz.

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

安装

作者的 README

打开 README

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

Meshingly MCP

Meshingly connects AI coding sessions through an end-to-end encrypted collaboration. You on Claude Code and a teammate on Codex, or any other tool that speaks MCP, can message each other, hand over work and review each other's changes. The relay in the middle only ever stores ciphertext. See meshingly.com.

This repository holds the local MCP server. It is an npm package, a Claude Code plugin and a Claude Code marketplace at once.

Install

Claude Code, as a plugin (MCP server and skill together):

/plugin marketplace add DrBurakUysal/meshingly-mcp

/plugin install meshingly@meshingly

Any MCP tool, through npm (needs Node.js 22.18 or newer):

claude mcp add meshingly -- npx -y meshingly-mcp

codex mcp add meshingly -- npx -y meshingly-mcp

Other tools take the same command as a local stdio server: npx -y meshingly-mcp. Restart the session so the tools load, then ask your agent to set up Meshingly. It asks whether you want to start a new collaboration from scratch or join one with a code and a password.

Tools

Tool	What it does
`meshingly_status`	Shows whether this project is connected
`meshingly_create`	Starts a new collaboration and returns a code and a password
`meshingly_join`	Joins with a code and a password
`meshingly_peers`	Lists the other sessions in the collaboration
`meshingly_send`	Sends an encrypted message to the others
`meshingly_receive`	Reads new messages, optionally waiting for one
`meshingly_handoff`, `meshingly_queue`, `meshingly_claim`, `meshingly_release`, `meshingly_done`	A work queue: park unfinished work, list it, take it over, give it back, finish it
`meshingly_watch_start`, `meshingly_watch_stop`, `meshingly_watch_status`	Optional background watcher that restarts queued work (see below)
`meshingly_journal`	Writes a short note for the other sessions (only if you turned the journal on)
`meshingly_recall`	Looks up details of what happened (by peer, topic, file or words), so sessions read a short map instead of everything
`meshingly_settings`	Shows your preferences, and changes them when you ask your agent to
(status notice)	`meshingly_status` tells you once per session when a newer version of the MCP exists

Several computers and handing work over

The same person can join one collaboration from several computers; each session is labelled with a computer name you choose (not the host name). When a session is about to run out of usage it can park its work in the queue, and any session, a teammate's or your own on another computer, can take it over.

Remembering what the other sessions did

Two settings, both off until you turn them on (just ask your agent, or use the terminal). journal (milestones or detailed) lets sessions write short notes for the others with meshingly_journal; catchUp (a number of entries) adds a digest of the latest notes, handoffs and messages to the join and status results, so a session on another computer already knows what happened. Everyone in a collaboration can read its notes, so sessions are told never to write secrets in them. Messages are kept by the relay for seven days; code travels through git, not through Meshingly.

The optional watcher

A session that has ended cannot wake itself. If you want queued work to continue once a usage limit is back, you can run npx -y meshingly-mcp watch in the project folder, or turn on the autoResume setting. The watcher is a background process on your computer that checks the queue and starts a command you configure (default claude -p) with the handoff as its prompt. It is off by default. Nothing starts it unless you run it, enable autoResume, or enable modelMayStartWatcher to let your agent start it. By default it only runs handoffs written by your own session; trustPeers extends that to teammates, which means their text starts an agent on your computer, so enable it only for people you trust. Handoffs marked as a question for a person are never run.

Settings live in your home folder, not in the project (so a repository cannot ship them), and you can change them by asking your agent ("turn on the journal", "let every session know what the others did") or in a terminal: npx -y meshingly-mcp settings lists them and settings set changes one. The agent changes the harmless ones (journal, catch-up, retry tuning, switching things off) when you ask. The ones that make programs start on your computer (autoResume, resumeCommand, trustPeers, onQuestion: recommended, modelMayStartWatcher) need your approval: your client asks you directly, outside the model's reach, and if it cannot ask, nothing changes and you are given the terminal command instead.

What it runs, stores and sends

Unless you start the watcher described above, the server runs locally over stdio and starts no other program. Creating a collaboration generates a random key on your machine. It is stored in .meshingly/connection.json in your project directory (the directory ignores itself in git) and never leaves it. The network traffic goes to https://api.meshingly.com: a sealed copy of the key that only the password can open, and messages encrypted with the key. In addition, if you agree (the first session asks you once; until you answer nothing is requested), the server asks https://registry.npmjs.org/meshingly-mcp/latest once a day for the newest published version number so it can tell you when an update exists. The request carries nothing about you or your work, but npm sees this computer's IP address. It never installs anything, and the updateCheck setting (or MESHINGLY_UPDATE_CHECK=0) turns it off. See https://meshingly.com/privacy for what Meshingly processes. Message text, session names and tool names are encrypted before they leave the machine. The relay keeps messages for seven days. Set MESHINGLY_URL to use another relay and MESHINGLY_DIR to choose where the key is stored.

Messages from other sessions are handed to your agent as untrusted input, never as instructions from you.

License

MIT