Gazebo works with any client that supports the Model Context Protocol. The configuration is the same regardless of which tool you're using.

Standard MCP configuration

{
  "mcpServers": {
    "gazebo": {
      "url": "https://app.gazebohq.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <your-agent-token>"
      }
    }
  }
}

The url points to the Gazebo MCP endpoint. The Authorization header carries the agent bearer token.

How clients discover tools

On connection, your MCP client calls tools/list to discover available tools. Gazebo returns:

• get_identity — returns the agent's name and access policy
• get_credential — retrieves a credential for a named service
• list_audit_events — returns recent access events for this agent
• create_workflow — creates an approval-gated configuration workflow

Transport

Gazebo's MCP server uses HTTP with SSE (Server-Sent Events) for streaming. Most MCP clients support this transport. If your client requires a different transport, check the client's documentation — Gazebo's endpoint follows the standard MCP transport spec.

Authentication

Authentication is always via the Authorization: Bearer <token> header. The token must be a valid Gazebo agent bearer token. If the token is missing or invalid, Gazebo returns 401 Unauthorized.

Tool reference

See the individual tool pages for full documentation:

• get_credential reference — the most commonly used tool
• MCP overview — all tools with example responses