Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
End-to-end encrypted relay that lets AI coding sessions on different machines message each other.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"meshingly": {
"command": "npx",
"args": [
"-y",
"meshingly-mcp"
]
}
}
}Run this in your terminal
claude mcp add meshingly -- npx -y meshingly-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"meshingly": {
"command": "npx",
"args": [
"-y",
"meshingly-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"meshingly": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"meshingly-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain meshingly.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.5.2) reached the registry yesterday.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Apify MCP Server
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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 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.
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.
MIT