A server is any MCP server you want your agents to reach — a git server, a
filesystem server, a database, an internal HTTP service. You register it with
Steerholm once; from then on it lives on the plane, and you decide which agents may
reach it by granting access.
Registering a server exposes nothing on its own. No agent can reach it until you
grant access — Steerholm is default-deny.
Register the server
Steerholm runs two kinds of MCP server: stdio servers it launches from a
command, and remote servers it connects to over HTTP. Give --command for one
or --url for the other — the type is inferred.
Pass configuration or secrets to a stdio server with --env (repeatable) — for
example a database connection string:
holm show server masks env values, so secrets don’t print back.
Confirm it’s running
list servers shows every server with its transport and live status; show server
adds the tools it provides and which agents have been granted access:
A healthy stdio server shows running with a tool count. If it never comes up, see
Troubleshooting.
Add more than one
Every server you add lives on the same plane — add as many as you need:
An agent connects to Steerholm in one place and sees only the tools its policy
allows, across every server it’s been granted. Wiring those grants is covered in
Managing access.
Remove a server
Removes the server from Steerholm and stops its process (for stdio servers). Agents
can no longer reach it: