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 Voter
Overview
Description from the maker (original English)
Vote-gated change control for WithVibe — the agent proposes a change via MCP; team approves first.
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 7, 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 18329 servers in this category
- Published to the registry more recently than 10% of the other 18329 servers in this category
- Basic checks equal to or better than 100% of the other 18329 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 Voter 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 (0.1.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, Excaliself
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 2 days ago
Install
Excaliself
by maciekzygmunt
Find, read, create, edit, and organize Excalidraw drawings in your self-hosted Excaliself instance.
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.
Voter — a WithVibe plugin
Turn any WithVibe env into a team-voted workspace. When this plugin is enabled, the AI doesn't apply a prompt straight away — it opens a proposal the team votes on, and only an approved proposal gets built. Enable it on any env and that env becomes a vote-gated sandbox.
You (in chat): "add a dark-mode toggle"│ ▼ voter_propose_change ──────► Proposal #7 opens (10-min vote) │ 👍 👎 team votes in the panel voter_await_decision ◄─────── APPROVED ✅ / REJECTED ✗ │ ▼ (only if approved) agent makes the change ──► voter_record_change ──► shows up in History
It's content-agnostic — it knows nothing about what the env contains. Whatever the env is (an app, a doc, a 3D scene, a config), enabling Voter makes every change go through the team first. Multiple envs = multiple independent boards.
How the gate works (and why it's just a plugin)
WithVibe auto-injects an enabled plugin's MCP tools into the agent's turn. Voter uses that to gate prompts without any change to WithVibe core:
voter_propose_change(prompt)— opens a proposal and tells the agent to not touch anything yet.voter_await_decision(proposal_id)— long-polls the vote. The platform's MCP bridge caps a single tool call at 60s, so this returns after ~45s withSTILL_VOTINGand the agent simply calls it again until it's terminal.- On
APPROVED, the agent makes the change and callsvoter_record_change. OnREJECTED/EXPIREDit makes no change.
Meanwhile every teammate votes in the plugin's own UI panel — independent of the agent. The gate is agent-cooperative (enforced via tool instructions), which is the right trade-off for a friendly workflow; hardening it to be unbypassable is a later option that would need a small core hook.
MCP tools
| Tool | Purpose |
|---|---|
voter_propose_change | Open a proposal for the requested change. Agent must call this instead of editing. |
voter_await_decision | Long-poll the team's verdict (APPROVED / REJECTED / EXPIRED / STILL_VOTING). |
voter_record_change | Record what shipped after applying an approved change. |
voter_report_failure | Mark an approved change as failed (e.g. build broke). |
voter_status | Show the current board: proposals in voting + recently resolved. |
State
Four tables in the plugin's isolated Postgres schema (shared-postgres storage): settings (vote window + thresholds), proposal, vote, feed_event.
Resolution rule: a proposal passes when approvals reach the threshold, fails when rejections reach the threshold, and at the deadline the majority wins (ties expire). Defaults: 600s window, 1 approval / 1 rejection — tune them in the panel.
Architecture
manifest.yaml ──► WithVibe spawns one container per env (scope: env)│ server.js (express) ├── /health platform health probe ├── /mcp agent's MCP endpoint ─► mcp.js (the gate) ├── /ui htmx voting panel ─► ui.js └── /ui/version cheap freshness check (live updates) │ db.js (pg) ─► shared-postgres, per-env schema
Build
docker build -t local/voter:0.1 .For the marketplace this is published multi-arch as ghcr.io/withvibe/voter: .
Install in WithVibe
- Workspace admin → Plugins → Install plugin (or Marketplace once listed).
- Paste manifest.yaml (or 1-click install from the catalog).
- Open any env → enable Voter → that env is now a vote-gated workspace.
Local development
docker build -t local/voter:0.1 .docker run --rm -p 8080:8080 \ -e DATABASE_URL="postgres://user:pass@host.docker.internal:5432/withvibe_plugins" \ -e PGSCHEMA="voter_dev" \ local/voter:0.1
open http://localhost:8080/ui — two browsers = two voters
Repository layout
manifest.yaml WithVibe plugin manifest (install input)Dockerfile runtime image package.json deps (express, pg, @modelcontextprotocol/sdk, zod) server.js express entry — HTTP + MCP routes + vote handling db.js pg pool, schema, proposal/vote/resolution helpers mcp.js the gate: propose / await / record MCP tools ui.js htmx voting panel + dark theme
License
Apache License 2.0. See NOTICE for attribution.