
Withvibe Voter
Turns WithVibe environments into team-voted workspaces where the agent can't apply changes until your team approves them. Instead of executing prompts directly, it calls voter_propose_change to open a proposal, voter_await_decision to long-poll the verdict, and only proceeds on approval. You get five MCP tools that gate the full workflow: propose, await, record, report failure, and status. Each enabled environment gets its own isolated voting board with configurable thresholds and time windows. The gate is agent-cooperative rather than hardened, which keeps the workflow friendly while still preventing surprise edits. Reach for this when you want humans in the loop before any AI-driven changes ship, whether that's code, configs, or content.
- tools
- 5
- last updated
- Jun 9, 2026
Tools
5 toolsPublic tool metadata for what this MCP can expose to an agent.
voter_propose_changeOpen a proposal for the requested change. Agent must call this instead of editing.
Open a proposal for the requested change. Agent must call this instead of editing.
No parameter schema in public metadata yet.
voter_await_decisionLong-poll the team's verdict (`APPROVED` / `REJECTED` / `EXPIRED` / `STILL_VOTING`).
Long-poll the team's verdict (`APPROVED` / `REJECTED` / `EXPIRED` / `STILL_VOTING`).
No parameter schema in public metadata yet.
voter_record_changeRecord what shipped after applying an approved change.
Record what shipped after applying an approved change.
No parameter schema in public metadata yet.
voter_report_failureMark an approved change as failed (e.g. build broke).
Mark an approved change as failed (e.g. build broke).
No parameter schema in public metadata yet.
voter_statusShow the current board: proposals in voting + recently resolved.
Show the current board: proposals in voting + recently resolved.
No parameter schema in public metadata yet.
Sponsors
Readme
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:
Details
- Repository
- github.com/withvibe/withvibe-voter
- Category
- AI & LLM Tools
- Registry
- MCP registry, active