Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP-native workflow engine: teach agents your processes once, they execute them consistently.
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.
PROGI_DB_PATHYou 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": {
"progi": {
"command": "uvx",
"args": [
"progi"
],
"env": {
"PROGI_DB_PATH": "your-value"
}
}
}
}Run this in your terminal
claude mcp add progi --env PROGI_DB_PATH=your-value -- uvx progiFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"progi": {
"command": "uvx",
"args": [
"progi"
],
"env": {
"PROGI_DB_PATH": "your-value"
}
}
}
}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": {
"progi": {
"type": "stdio",
"command": "uvx",
"args": [
"progi"
],
"env": {
"PROGI_DB_PATH": "your-value"
}
}
}
}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.
PROGI_DB_PATH envThese 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 zseta, 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 (0.3.2) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Symantec Cloud DLP AIops
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.
Governed Symantec Cloud DLP — 14 MCP tools, read-only with audit.
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.
Progi teaches your agent how you like to get things done. So you can do your best work without re-explaining your process or losing context between sessions.
Add Progi to your MCP client config (GH Copilot / Cursor / Claude Code / etc):
{
"mcpServers": { "progi": { "command": "uvx", "args": ["progi"] } } }
Progi Monitoring starts automatically at http://127.0.0.1:8000.
If you want to start Monitoring on a different port:
{
"mcpServers": { "progi": { "command": "uvx", "args": ["progi"], "env": { "PROGI_WEB_PORT": "8080" } } } }
1. Describe your workflow
*"Hey Progi, help me create workflow for creating integrations, reviewing code, and publishing PRs."*
Describe your process in plain language. You can be detailed or just provide a rough idea. Progi stores it as a structured workflow with per-step playbooks.
2. Run tasks, stay in the loop
*"Hey Progi, start a new task, we need to review a new docs PR in the repo."* Your agent loads the workflow, works through each step using your playbooks, and loops you in at critical checkpoints to review output.
3. Monitor progress
Progi Monitoring gives you a live view of every running and completed task — status, progress, and the full output history across all your workflows.
4. Optimize as you go
Tweak playbooks in Progi Monitoring between runs. Because workflows live in a database and survive context resets, every future task picks up your changes automatically — your process gets sharper with each iteration.
| Tool | Description |
|---|---|
create_task | Create a new task under a given workflow (status todo); returns a preview of its first step |
list_tasks | List tasks, optionally filtered by status and/or workflow |
start_or_continue_task | Main work-loop entry point — starts or resumes a task and returns the current step's playbook, input data, and output spec |
update_progress_notes | Overwrite a task's progress notes (mid-step save point) |
finish_step | Mark the current step complete, store its output, and advance to the next step (or mark done) |
| Tool | Description |
|---|---|
get_process_skeleton_prompt | Return the Pass 1 system prompt for turning a plain-language description into a structured workflow skeleton |
get_playbook_authoring_prompt | Return the Pass 2 system prompt for authoring a step's playbook (injects workflow context) |
save_workflow | Persist a new workflow, its steps, and playbooks |
list_workflows | Return all workflows with their ordered steps |
Authoring is two passes: Pass 1 turns a plain-language description into a structured skeleton; Pass 2 authors each step's playbook. save_workflow persists both.
| Variable | Default | Purpose |
|---|---|---|
PROGI_DB_PATH | OS data dir (platformdirs) | SQLite file location |
PROGI_WEB_HOST | 127.0.0.1 | Web UI bind host |
PROGI_WEB_PORT | 8000 | Web UI port |
PROGI_NO_WEB | 0 | Set to 1 to disable the web UI |
Run modes: uvx progi (MCP + web UI), uvx progi --no-web (MCP only), uvx progi-web (web UI only).
Use an absolute path for
PROGI_DB_PATH