Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Keeps an AI coding agent on its plan across context compression, with a live local dashboard.
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": {
"progressor": {
"command": "npx",
"args": [
"-y",
"progressor-mcp"
]
}
}
}Run this in your terminal
claude mcp add progressor -- npx -y progressor-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"progressor": {
"command": "npx",
"args": [
"-y",
"progressor-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": {
"progressor": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"progressor-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 with the GitHub account racstan, which owns the repo
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 (1.2.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, topo^alpin
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.
Avalanche bulletins and mountain weather forecasts for any place in the Alps.
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.
Progressor
Your AI's plan, saved in your project and shown live, so neither you nor your AI ever loses track of the work.
The problem: AI chats forget. When a long chat gets its memory compressed, or you start a new chat, the AI no longer knows what was planned, what's done or what's left, and you end up explaining it all again.
What Progressor does: your AI writes its plan, a goal with steps, into your project folder and keeps it up to date as it works. After a chat is compressed, or in a new chat, even in a different AI app, say *"use Progressor"* and your AI reads that plan and carries on where the work stopped. And you see the same plan on a page in your browser that updates by itself: what the AI is doing right now, what's done, and what it needs from you.
▶ Watch the 4-minute video on YouTube
It works with any app that supports MCP (the standard way AI apps add tools): Claude Code, Claude Desktop, VS Code with Copilot, Cursor, Windsurf, Codex and others.
Every step, live What the AI is working on is highlighted and moves; finished steps say when they were done. A side trip shows where the AI stepped off the plan, and why.
The plan as a map Each step is a stop on a line. Side trips branch off and rejoin, and steps they add join the route, so you can see how the plan changed.
It says when it needs you A question, a step to check, something to try on your phone: it all waits in Needs you , and you answer with a click. Your AI sees your answer at its next step.
Talk to your AI from the page Write to your AI about one goal or the whole project, and its replies show up under your messages. What you write stays on your computer, out of git.
Statistics How long steps take against their estimates, how often the work drifts, and what got done each day, for each project and for all of them on Home.
Rules your AI keeps "Always ask before adding a dependency." Lasting rules and the project's background live in Project notes . Add, change or remove them there, and your AI is told.
Every project on one page Home shows what needs you and what's being worked on across all your projects, in any app, with statistics for all of them.
Light, dark or colourful A calm black-and-white look in light or dark, or Vibrant if you like colour. See dark .
AI chats forget. A long chat gets its memory compressed, a new chat starts from nothing, and switching to another app or AI tool usually means explaining your project all over again. With Progressor, none of that costs you your progress:
You need Node.js 22 or later. Then paste this into your AI's chat, in the project you're working on:
Set up Progressor (https://github.com/racstan/progressor-mcp) for this project:
node --version. If it is older than 22, stop and tell me how to install Node.npm install -g progressor-mcp.progressor-mcp init --yes in this folder. Otherwise, add the "progressor" MCP server to this app's settings as the guide for this app shows (https://github.com/racstan/progressor-mcp/blob/main/docs/apps.md), then run progressor-mcp init --yes --no-server in this folder.
Your AI does the rest. To have Progressor in every project without setting each one up, add it once to your app's settings for all projects (how, for each app). If you'd rather do it yourself, Getting started walks through it, and Setup for your app has the exact settings for each app.
Tell it what you want to build, as you would anyway: *"Add a login page with Google sign-in."* It plans the work as a goal, shows you the steps, and starts. You don't need to learn any commands. If you want to nudge it, these work in most apps' / menu:
| Command | What it does |
|---|---|
/progressor:next | Carry on where the work was left |
/progressor:status | Where things stand, in a few lines |
/progressor:plan | Plan something new together |
/progressor:dashboard | The dashboard's link |
/progressor:review | Check a goal against what finished looks like, and add steps if something is missing |
/progressor:setup | Set Progressor up in this project |
Open http://localhost:4747 while your AI's app is open (your AI gives you the link).
More in the dashboard guide.
Most problems can be fixed by asking your AI. Troubleshooting lists the common ones, each with a line you can paste to your AI. Still stuck? Report a problem, or use ❓ Help on the dashboard, which fills in your version and system for you.
Only the beginning is shown; read the rest in the repo