One static Go binary that serves many MCP servers through a single MCP endpoint, with a web panel.
A client that talks to a dozen MCP servers pays for a dozen tool lists in its context before it asks anything. mcprig puts them behind nine meta-tools, groups servers into named sets, runs each set as its own process with its own port and key, and manages the whole registry from a web panel.
- Nine meta-tools instead of a whole tool catalogue
- One endpoint, one key per named set
- Registry, keys and live call tail in the panel
- Set composition, import/export, and a ready-to-paste agent prompt built from a set's tools
- Sandbox for stdio servers, OAuth for remote ones
- One static binary, no runtime dependencies
Documentation: docs/en — install, configuration, CLI, panel, meta-tools, architecture. Русский: docs/ru.
Release archives cover linux and darwin on amd64 and arm64. Linux amd64:
curl -LO https://github.com/akrhin/mcprig/releases/download/v0.6.3/mcprig_0.6.3_linux_amd64.tar.gz
tar -xzf mcprig_0.6.3_linux_amd64.tar.gz
MCPRIG_PASSWORD=change-me ./mcprig panelOpen http://localhost:9091, sign in as admin, add a server, add a set that
contains it, press Start, then issue a key for the set. The panel shows the
token once; save it where only you can read it:
umask 077; printf '%s' '<token>' > demo.keyThe panel: sets on their own ports and endpoints, the servers of one set, and its traffic for the last 7 days.
Docker works the same way, with no Go toolchain needed:
docker pull ghcr.io/akrhin/mcprig:latest (latest-full adds node and python for
npx/uvx downstreams). systemd units, archive contents and the state
directory: docs/en/install.md.
init prints a fragment for the client's own config file and never edits it:
./mcprig init --client claude --set demo \
--remote http://127.0.0.1:9100/mcp --key-file ./demo.key{
"mcpServers": {
"mcprig-demo": {
"type": "http",
"url": "http://127.0.0.1:9100/mcp",
"headers": {
"Authorization": "Bearer <token>"
}
}
}
}--client opencode prints mcp JSON, --client codex prints a TOML table. The
port in an endpoint is the set's own: the set header shows it as a chip and the
top bar prints the full endpoint
(docs/en/panel.md). For a
client that spawns the binary itself, drop --remote and pass --config with
that set's servers.json instead: the fragment then runs mcprig stdio with no
port and no key. The panel writes a set's config into its state directory —
$MCPRIG_DATA_DIR/sets/demo/servers.json, with MCPRIG_DATA_DIR defaulting to
~/.local/state/mcprig — while ~/.config/mcprig/sets/demo/servers.json is the
file the mcprig-set@ systemd unit runs
(docs/en/install.md). Both forms with real
output: docs/en/cli.md.
Client → one set endpoint → nine meta-tools (five work with servers, four serve
resources and prompts) → the downstream servers of that set.
The panel supervises one mcprig serve process per set, so a restart or a crash
of one set leaves the others serving. Every picture below opens interactively
(themes, zoom, PNG/SVG export) by a click on it, and the spec it is generated
from sits next to it as .json.
How it compares with other proxies and where it stays weaker: docs/en/alternatives.md.
A set is one servers.json in the lazy-mcp format, read as-is: servers[] with
command or url, plus env, headers, sandbox, transport,
permissions. The panel writes the same file for the sets it runs, so a config
made by hand and one made in the browser are not two formats.
"sandbox": {} puts a stdio server under bubblewrap: read-only root, no
/home, no network, prlimit limits. A server tagged untrusted cannot start
without it. Field reference and what the sandbox does not limit:
docs/en/configuration.md.
A set with no authToken refuses to start unless it is explicitly open; the
panel password is constant-time compared with rate limiting per IP; tokens are
returned in full once and as a prefix afterwards. Auth modes, host policy,
permission rules, limits and the 4 MiB body cap:
docs/en/configuration.md and
docs/en/panel.md.
Pre-1.0, single operator: one panel, one password, no per-user roles. CLI help and log lines are Russian.
Issues and pull requests follow CONTRIBUTING.md. Security reports: SECURITY.md.
MIT, see LICENSE.



