Install and auth checks
Expose setup commands and OAuth steps inside the CLI instead of assuming every user knows how to wire a server.

MCP · tools · OAuth
Muster treats MCP as a capability surface: installable servers, setup guidance, OAuth hints, include/exclude policy, result caps, circuit breakers, and token-ledger evidence.
MCP controls
Expose setup commands and OAuth steps inside the CLI instead of assuming every user knows how to wire a server.
Keep tool access deliberate with configured allowlists, result-size limits, and circuit breakers.
MCP results flow through the same scoped memory and token ledger as normal agent turns.
GitHub, Notion, Google Drive, Postgres, browser, web search, and custom stdio/http servers fit this model.