Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-yehudalevy-collab-polis-protocol": {
"args": [
"polis-protocol"
],
"command": "uvx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
The local-first control plane for coding agents. Run Claude, Codex, Gemini, and Cursor against one repo — every task gets an owner, every handoff carries evidence, and the team measurably stops repeating its own mistakes. Plain markdown, in git, across every vendor.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
uvx 'polis-protocol' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked polis-protocol against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in maps
Open-source toolkit for the QVeris capability routing network: CLI, MCP server, Python SDK, skills, and REST API docs for agents to discover, inspect, call, and audit real-world tools.
Real-time BART departures, trip planning, fares, stations, and advisories.
Hawaii MCP: tours, events, weather, restaurants, and day-plan itineraries across 4 islands.
Real-time SF Muni departures, routes, alerts, vehicle positions, and schedules.
MCP Security Weekly
Get CVE alerts and security updates for io.github.yehudalevy-collab/polis-protocol and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
The local-first control plane for coding agents. Run Claude, Codex, Gemini, and Cursor against one repo — every task gets an owner, every handoff carries evidence, and the team measurably stops repeating its own mistakes. Plain markdown, in git, across every vendor.
🌐 Website → polis-protocol.vercel.app · Install · Proof · Plug into your agent (MCP)
Repeat errors: 65% → 7% (−89%) · Collisions: 0, deterministic · reproduce in 5s: polis bench --mode learning
Yes — we benchmarked our own tool and published where it loses. That candor is the whole pitch.
uvx polis-protocol init # one command · no server · no database · just markdown in your repo
Shared by Claude · Codex · Gemini · Cursor, all reading one _polis/ folder. MIT.
⭐ If the loop below clicks, a star helps other multi-agent builders find this.
Three AI agents share one project: Claude (research), Codex (frontend), Gemini (translation).
A Spanish-translation task comes in. Who gets it?
Early on, Claude did — it rated itself highly. But two finished contracts and one lesson later ("the corporate word 'líder' reads wrong here; use the movement loan-word 'madrij'"), the router quietly moved that work to Gemini. Nobody reassigned it. The team learned, and the routing followed.
That loop — work routed by track record, track record updated by outcomes — is the entire point. See it yourself in one command, no install, no API keys:
git clone https://github.com/yehudalevy-collab/polis-protocol.git
cd polis-protocol && bash scripts/demo.sh
Score breakdown (sorted by total):
gemini-translator-pesaj total=0.688 hist=0.25 self=1.00 cost=1.00 avail=1.00 lessons=+0.10
↳ lessons applied: 2026-04-18-madrij-not-lider
claude-research-pesaj total=0.453 hist=0.15 self=0.60 cost=1.00 avail=1.00 lessons=+0.00
codex-frontend-pesaj total=0.290 hist=0.00 self=0.20 cost=1.00 avail=1.00 lessons=+0.00
Recommendation: gemini-translator-pesaj ← won on history + an applied lesson, not self-rating
If that loop is interesting to you, a ⭐ genuinely helps other multi-agent builders find this.
There is now a wave of git-and-markdown task boards for AI agents — claim a task, do it, mark it done. They're good, and