Skip to Content
Agent ClientsCoding agents

Connect Crush to Agent Authority

Connect Charm's Crush to SecureAuth Agent Authority with OAuth sign-in so every MCP tool call is checked and audited

When you finish, every MCP tool call Crush makes is checked against your policies and recorded in the audit log. Crush, Charm's coding agent for the terminal, reaches your approved tools through one SecureAuth Agent Authority gateway URL, and each developer signs in as themselves.

Setup

  1. Add the MCP server. Add the following to ~/.config/crush/crush.json:

    {
      "mcp": {
        "secureauth": {
          "type": "http",
          "url": "https://your-gateway-url/gateway/mcp",
          "oauth": true
        }
      }
    }

    "oauth": true turns on Crush's OAuth sign-in for this server. Crush reads the scopes to request from the gateway, so you don't list them.

  2. Authenticate. Start Crush (crush). It opens an Authenticate with secureauth dialog: press Enter, and a browser window opens for sign-in. Crush saves the token, so you sign in once.

  3. Start using. The secureauth server shows its tool count in the sidebar, and Crush asks before each tool call as usual.

    The agent is auto-registered on first connect.

Crush connect steps in the console
The Crush steps in the console carry your gateway URL.

Connecting to just one MCP? To stay under an agent's tool limit, point the URL at a single MCP — /gateway/mcp/{slug} instead of /gateway/mcp. Grab the exact URL from the resource's detail page; see Scope a connection.

Next steps

Crush now reaches your tools through the secureauth server in ~/.config/crush/crush.json. Next, write the policy that decides which tools it can call.

On this page