Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Withvibe Roadmap
Overview
Description from the maker (original English)
Per-env roadmap board for WithVibe — an MCP server the orchestrator drives to plan and track work.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: –
- Transport:
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
The maker has not listed install details in the registry. See the maker’s README below.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
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
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account withvibe, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 32505 servers in this category
- Published to the registry more recently than 12% of the other 32505 servers in this category
- Basic checks equal to or better than 100% of the other 32505 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Withvibe Roadmap safe?
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.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
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).
Is it still maintained?
The GitHub repo last changed –, and the latest version (2.0.0) reached the registry 5 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, topo^alpin
Alternatives
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
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated yesterday
Install
topo^alpin
by topoalpin.app
Avalanche bulletins and mountain weather forecasts for any place in the Alps.
Runs in the cloudUpdated today
Install
README from the maker
Open the README
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.
WithVibe Roadmap Plugin
A per-env implementation roadmap board for WithVibe — Postgres-backed, with an MCP server the AI orchestrator drives directly.
Multi-phase features drift. Plans change mid-flight. After a few sessions you lose track of what shipped, what's pending, and which step you're actually on. This plugin gives the AI a structured place to keep that state — and the user a live view of it.
Feature: Auth rewrite ▓▓▓▓░░░░░░ 4/11 tasksyou are here → API layer › Wire DTO validation
[x] Phase 1: Schema (done) [~] Phase 2: API layer (in progress) [x] Endpoint scaffolding [x] Auth guard [~] Wire DTO validation ← active [ ] Error envelope [ ] Phase 3: Web [ ] Phase 4: QA
— Plan changes — 2026-05-28 AI added Phase 4 (QA) — reason: integration tests not in original scope 2026-05-29 user removed "Add caching" — reason: deferred to follow-up
What's in the box
- Hierarchical roadmap — feature → phase → task, with
pending / in_progress / done / blocked / deferred / canceledstatuses. - "You are here" marker — exactly one task is active at a time; the banner is the recovery anchor when you context-switch back.
- Plan-change log — every add/remove/rename/status-change records an actor (
aioruser) and an optional reason. The trail makes drift visible. - MCP tools the AI orchestrator uses without prompting:
propose_plan,set_active_task,complete_task,add_note,update_task,log_change, … - Live UI — htmx-based, polls a tiny version endpoint so the iframe updates within ~4s of any AI change without scroll jumps.
- Persistent — uses WithVibe's
shared-postgresplugin storage, so state survives container restarts.
Architecture
manifest.yaml ──→ WithVibe spawns one container per env↓ server.js (express) ├── /health platform health probe ├── /mcp AI orchestrator's MCP endpoint ─→ mcp.js ├── /ui dark-themed htmx UI ─→ ui.js └── /ui/version cheap freshness check (drives live updates) ↓ db.js (pg) ↓ shared-postgres per-env schema plan / phase / task / plan_event
- Scope: `env` — one container per (env, plugin). Each env gets its own roadmap, its own Postgres schema, its own port.
- Storage:
shared-postgres— the platform provisions a dedicated role + schema in thewithvibe_pluginsdatabase and injectsDATABASE_URL+PGSCHEMAat spawn. The plugin role can't reach the mainwithvibeDB. - State surface: four tables in db.js —
plan(singleton),phase,task,plan_event(change log).
MCP tools
All tools return the full updated plan in the trailing text so the AI never holds stale state.
| Tool | Purpose |
|---|---|
get_plan | Read the full roadmap + active marker + last 20 events. |
propose_plan | Replace the whole roadmap (initial planning or a major re-plan). |
add_phase / add_task | Append work mid-flight; reason recorded. |
set_active_task | Mark the "you are here" anchor before starting work. |
complete_task | Mark done with a 1-line outcome; auto-closes the phase if every task is done. |
update_task / update_phase | Edit title/description/status (blocked, deferred, canceled) with reason. |
add_note | Append a markdown note — decisions, things tried, references. |
log_change | Narrate a plan-level decision without mutating data. |
See mcp.js for the full schemas.
Build
docker build -t local/roadmap:2.0 .The image is multi-arch-friendly via Node 20 Alpine, ~150 MB, no native build steps.
Install in WithVibe
- Workspace admin → Plugins → Install plugin.
- Paste the contents of manifest.yaml into the editor.
- The platform pulls / locates the image and registers the plugin.
- Open any env → the Roadmap tab appears in the plugin panel.
To update after rebuilding the image, hit Update on the plugin row in the admin list — running instances are stopped so the next env start picks up the new image.
Manifest
The manifest is the entire install input. The fields that matter for this plugin:
id: withvibe.roadmap # URL + tool prefix; reverse-DNS-ishname: Roadmap # display name in the env's plugin panel version: 2.0.0 icon: list-todo # Lucide icon image: local/roadmap:2.0 # OCI ref
scope: env # one container per env storage: kind: shared-postgres # platform-managed Postgres role + schema
ui: path: /ui # iframe entry point websocket: false
mcp: enabled: true path: /mcp # MCP endpoint the AI auto-discovers
Local development
# Builddocker build -t local/roadmap:2.0 .
Run standalone (requires a Postgres reachable via DATABASE_URL)
docker run --rm -p 8080:8080 \ -e DATABASE_URL="postgres://user:pass@host.docker.internal:5432/withvibe_plugins" \ -e PGSCHEMA="roadmap_dev" \ local/roadmap:2.0
Then open http://localhost:8080/ui
When developing against a real WithVibe install, hit Update in the admin Plugins page after each rebuild — that stops running instances so the next env start picks up the new image.
Repository layout
manifest.yaml WithVibe plugin manifestDockerfile builds the runtime image package.json npm deps (express, pg, @modelcontextprotocol/sdk, zod) server.js express entry, HTTP + MCP routes db.js pg pool, schema init, query helpers mcp.js MCP tool registrations ui.js htmx UI rendering + dark-themed CSS
Contributing
Issues and PRs welcome. Keep changes focused and document the *why* in commits.
License
Apache License 2.0. See NOTICE for attribution.