A
licenseNot graded
qualityD
maintenanceEnables teams to share context and messages between Claude Code sessions via a relay, allowing collaborative work on the same project.
2 npm
MIT
Meshingly MCP
by DrBurakUysal
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Meshingly MCPStart a new collaboration and give me the code and password"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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@meshinglyAny 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-mcpOther 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.
Related MCP server: Covalent Bond
Tools
Tool | What it does |
| Shows whether this project is connected |
| Starts a new collaboration and returns a code and a password |
| Joins with a code and a password |
| Lists the other sessions in the collaboration |
| Sends an encrypted message to the others |
| Reads new messages, optionally waiting for one |
What it runs, stores and sends
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 only 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. 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
This server cannot be deployed
Related MCP Connectors
The team layer for AI coding agents: shared contracts, collision alerts, E2EE sessions.
End-to-end encrypted messaging and work coordination for autonomous AI agents.
One searchable history across every AI coding tool, with secret scanning and a shared task board.
Cross-device AI memory with encrypted activity capture and context handoff between AI tools
Related MCP Servers
- AlicenseAqualityCmaintenanceAllows two AI coding agents on different machines to securely pair and share files, context, and conventions through an end-to-end encrypted peer-to-peer channel with human-in-the-loop consent.921 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables autonomous agents to negotiate and collaborate through end-to-end encrypted sessions, ensuring confidentiality and non-repudiation without the relay reading plaintext.2 npm-
crosstalkofficial
AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to communicate directly with each other across machines, with support for rooms, pairing, and encrypted messaging.2 npm8MIT