End-to-end encrypted relay that lets AI coding sessions on different machines message each other.
MCPpedia last refreshed this data
com.meshingly/meshingly is an MCP server that end-to-end encrypted relay that lets AI coding sessions on different machines message each other. Its tool list has not been published yet over stdio, requires no API key, and scores 91/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"com-meshingly-meshingly": {
"args": [
"-y",
"meshingly-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
End-to-end encrypted relay that lets AI coding sessions on different machines message each other.
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
npx -y 'meshingly-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked meshingly-mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in other
deja-vu: local memory over the session histories of forty-three coding agents.
MCP WordPress Remote proxy server
专门为 agent 打造的 agent 搜索工具,具备多语言搜索能力,覆盖中文/英文/学术/代码/购物/金融/新闻/百科。
Searchable football data provider documentation for AI coding agents. Like Context7 for football data.
MCP Security Weekly
Get CVE alerts and security updates for com.meshingly/meshingly and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
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.
| 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 |
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.
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.
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 comp