Any MCP client

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

Connection details

Configure your client with the endpoint https://app.gazebohq.com/api/mcp and an Authorization: Bearer <your-agent-token> header. Create the agent bearer token at Agents. Client configuration formats differ, so follow the client's current documentation for the appropriate configuration location and field names.

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

Transport

Gazebo uses stateless, JSON-only Streamable HTTP over POST. It does not use GET, SSE, sessions, or server streaming.

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.

Credential handling

get_credential delivers a credential value to the MCP client/agent. Use it only for the required operation and do not persist it in files, environment variables, logs, prompts, or long-lived memory.

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