Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Hand tasks, bugs and finished work to AI coding agents, and get back a write-up with evidence.
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 …”.
Works in Claude on the web, desktop and mobile:
https://passalong.dev/v1/mcpOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"passalong": {
"command": "npx",
"args": [
"-y",
"passalong",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add --transport http passalong https://passalong.dev/v1/mcpclaude mcp add passalong -- npx -y passalong mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"passalong": {
"url": "https://passalong.dev/v1/mcp"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"passalong": {
"command": "npx",
"args": [
"-y",
"passalong",
"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": {
"passalong": {
"type": "http",
"url": "https://passalong.dev/v1/mcp"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"passalong": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"passalong",
"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.
ChatGPT connects only to servers on the internet:
https://passalong.dev/v1/mcpMenu names can differ slightly by plan and over time.
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.
We have not read this server’s tool list yet; we check endpoints in rotation.
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 with the GitHub account codellyson, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
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.
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (0.13.1) reached the registry 35 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Reelsaw
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.
Drive a self-hosted Reelsaw: turn long videos into vertical clips, edit, re-render and export them.
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.
Work for your team and its AI agents, and what they know.
Say what needs doing once — in a sentence, with a screenshot, from email or a webhook. Whoever it is for, a person or their agent, takes it, says how it is going, and hands it in with the evidence, and it is Done. What the agent learned goes into the project's documents, where the next one finds it. Everyone can see who has what. Works with Claude Code, Codex, ChatGPT, Claude, or anything that speaks MCP or HTTP. See passalong.dev.
npm i -g passalong
passalong setup # the Claude Code capture skill, the MCP server and hooks passalong login # approve this machine in the hub; no password typed codex mcp add passalong -- passalong mcp # Codex: the same MCP server
passalong new "the upload button does nothing", the hub's box, or an agent's create_work. Work has no kinds and no required sections: a title, a one-line summary, and whatever the next reader needs. It is Ready at once unless you say --draft.passalong take (or take with no id for the next one here) holds it: nobody else can take it while you do, and whoever sent it sees you are on it.passalong progress "migration written". Stuck or not yours: passalong pass . Need an answer: passalong ask .passalong hand-in --evidence "npm test: 42 passing". It goes to Done with what you showed; a person can reopen it with a reason if it is not right./passalong-capture: the skill writes it into the project's documents and a line on its Log.passalong new "<what needs doing>" [--to TARGET] [--parent ID] [--draft] write work down
passalong new [--to TARGET] [--parent ID] [--draft] the same, from a file passalong board what needs you, who is on what, and what is ready passalong list [query] work you and your teams can see, newest first passalong open [--print] view work in the browser (or the terminal) passalong take [id] [--save] you are doing it; --save also writes ./.passalong/ .md (git-ignored) passalong progress still on it, with a one-line note the hub shows passalong hand-in --evidence TEXT [--writeup TEXT] [--pr LINK] it is done passalong pass not yours, or stuck: hands it back with your reason passalong ask ask the person, keep it, and wait for their answer passalong reply write to whoever holds it (--file PATH to attach); or leave a note passalong assign give it to @handle (or several), a #group, or "team" passalong release take work back from whoever holds it passalong reopen finished work isn't right: back to To do, with why passalong ready drafts you have read are Ready passalong archive off the board and out of the free tier's count passalong rm delete it passalong attach upload a picture or file and print the markdown that points at it passalong work [--once] [--agent CMD] run an agent on each piece of ready work here, in turn passalong work --watch the runner: work a person marked safe to run alone, up to 3 at once and 10 a day, each in its own worktree, finished as a pull request passalong now what this worktree holds and what is waiting passalong hub open the hub in the browser passalong export [dir] every piece of work as plain markdown passalong login [--new | --with-token] sign in from the browser, add an account, or read a token passalong accounts | use | logout [name] the accounts on this machine passalong me [--handle H] [--name N] [--email E] who you are to teammates passalong team [create | invite [email] | join | use ] teams passalong setup install the capture skill, MCP server and hooks passalong mcp run the MCP server over stdio passalong version print the installed version (also -v, --version)
A team is where work goes. Everyone in it sees the same board; work can be sent to one person (--to khaime/@ada), a group (--to khaime/#frontend) or the whole team, and whoever it names is told — by email too, when the server has mail configured.
passalong me --handle lukman # how teammates address you
passalong team create Khaime # you become owner; "khaime" is now current passalong team invite ada@example.com # or no email: prints a link to send yourself passalong new "Fix the upload button" --to khaime/@ada passalong board # on Ada's side: what needs her
Invites are accepted in the browser, so a teammate needs no terminal to be part of a team.
passalong setup registers the server with Claude Code. For other clients, run passalong mcp over stdio, or add the hosted server at https://passalong.dev/v1/mcp.
Seventeen tools over four nouns. Work: take, progress, hand_in, pass, ask, create_work, find_work, update_work. Projects and their documents: find_projects, save_project, read_document, save_document, delete_document. Files: add_file, read_file, delete_file. And accounts, for a machine signed in more than once.
Plain markdown with frontmatter, held on the server; nothing piles up on your machine. Ask for a file when you want one: passalong take --save, or passalong export for everything.
Point at a self-hosted server with PASSALONG_API=https://your-host before passalong login.
A machine can be signed in to several accounts, say a work one and a personal one. passalong login --new adds another beside the first, passalong accounts lists them, and passalong use picks the default a person at a terminal gets.
An agent has no terminal to be asked at, so with two or more accounts and nothing saying which, it is refused and told to ask you. It puts the question to you in plain words, you answer, and it calls accounts with use and the name. That lasts for the session and moves nothing on disk. From a shell, --as or PASSALONG_ACCOUNT= says the same for one command. The team you work in (passalong team use) belongs to the account, not the machine.