Erbina MCP server

erbina

A Claude-Code-only MCP server that bootstraps your dev environment from one

prompt — install, wire, and verify CLI tools and other MCP servers from

curated recipes, and see where every MCP server lives across your scopes.

Named after the Lusitanian goddess of boundaries and crossings — erbina is the threshold a tool crosses to become part of your environment. Sibling to ataegina (goddess of rebirth), which is also erbina's proof-of-concept recipe #1.

The recipe contract is the core idea. One server, eleven tools, and a curated

set of 500+ recipes spanning cli-tools, scope-wiring mcp-servers, and

profiles that bundle them (see the Recipe gallery). Each is

one YAML file held to a conformance bar — schema + linter policy + a 100%-covered

offline suite, plus a weekly job that actually installs it on macOS, Linux, and

Windows — and adding one is the point.

Why this exists

Setting up a coding-agent environment is death by a thousand cuts: you install a CLI, hand-edit a config, add an MCP server — then find out it's in the wrong scope and isn't showing up. Claude Code spreads MCP config across up to four files in two apps, with no single place that knows what's installed where (anthropics/claude-code#27458, #8288, #5963).

erbina makes setup a thing an agent does for you, and proves worked:

point — run it by hand and you get nothing. Nobody mistakes it for a manual installer that "should just work."

• It's an MCP server, so an agent must drive it. There is no human entry

detect → install → configure → verify. Idempotent by construction — it detects what's already there and skips it, and success means the tool runs, not that a line was written to a file. Recipes also compose (requires: prerequisites, profiles that bundle a whole set) and cover the full lifecycle: update → re-verify → rollback, uninstall, and a doctor health-check over everything erbina installed.

• Recipes, not one-shot installs. Each entry is a contract:

scopes, wires MCP-server recipes into the right one, and audits all three so you finally have one place that answers "what's installed, and where?"

• Scope-aware. It knows about Claude Code's local / project / user

on-demand) CI job bootstraps recipes for real against live package managers on macOS, Linux, and Windows — so a renamed brew formula, a dead URL, or a bad winget id is caught, not shipped.

• Proven, not just written. On top of the offline suite, a weekly (and

Install

erbina is a single Python file run by uv (it declares its own dependencies inline — no venv to manage).

git clone https://github.com/noahhyden/erbina
# register it with Claude Code (use --scope user to make it available everywhere)
claude mcp add erbina --scope user -- uv run --script /absolute/path/to/erbina/server.py

Shortened. The full README is on GitHub.