Meshingly

Official registry Developer tools

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

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package meshingly-mcp
Claude Code
claude mcp add meshingly -- npx -y meshingly-mcp@0.1.0
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "meshingly": {
            "command": "npx",
            "args": [
                "-y",
                "meshingly-mcp@0.1.0"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Meshingly MCP
  2. Install
  3. Tools
  4. What it runs, stores and sends
  5. License

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

ToolWhat it does
meshingly_statusShows whether this project is connected
meshingly_createStarts a new collaboration and returns a code and a password
meshingly_joinJoins with a code and a password
meshingly_peersLists the other sessions in the collaboration
meshingly_sendSends an encrypted message to the others
meshingly_receiveReads 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

Frequently asked questions

What is Meshingly?

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

How do I install Meshingly?

It runs on your machine. In Claude Code: claude mcp add meshingly -- npx -y meshingly-mcp@0.1.0. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Meshingly need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Meshingly open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Meshingly?

It is published by DrBurakUysal. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.