eidos-mcp-registry

What it does

You have 20+ MCP servers installed. You work across 100+ repos. Every server leaks into every project — staging credentials visible in client repos, internal tools cluttering projects that don't need them, Claude burning thousands of tokens evaluating 200+ tools when it only needs 20. The registry fixes this.

Key features

• Group-based scoping — organize servers by client, team, or project. Client A's repos only see Client A's tools
• One-click deploy — write .mcp.json to every repo in a group. Merge-safe: hand-edits preserved
• Secrets masking — API keys automatically replaced with $VAR references. Secrets never touch disk
• Scope audit — see which servers are leaking to unintended projects. One-click fix
• Token budget — see exactly how many tokens you're burning on tool schemas
• Snapshot + rollback — every deploy creates a restore point
• 280+ tests — unit, API, and E2E (Playwright)

Install

pip install eidos-mcp-registry

The lifecycle

# 1. Scan — discovers servers from claude mcp list + project configs
# 2. Assign — drag servers into groups (each group = a set of repos)
# 3. Deploy — write .mcp.json to every repo in a group
# 4. Promote — remove from global config, only exist where assigned

Scan -> Assign -> Deploy -> Promote

Built for Claude Code. Local UI for organizing, deploying, and auditing MCP server configs across your entire workspace.