Gazebo
    ServicesAgentsDocsSpecWritingPricing
    Log inSign up
    Log in

    Getting Started

    • Introduction
    • How Gazebo works
    • Core concepts
    • Quickstart

    Agent Access

    • Access profiles
    • Bearer tokens
    • Audit logs

    MCP

    • Overview
    • Cursor
    • Claude Code
    • Windsurf
    • Any MCP client
    • Get credential reference

    Open Standard

    • Agent Consent Flow
    • Agent Identity Protocol (AIP) ↗

    REST API

    • Overview
    • Authentication
    • Services
    • Agents
    • Access policies
    • Audit events
    • Consent administration
    • Agent credential access
    • Errors and limits

    Security

    • Overview
    • Encryption model
    • Credential storage
    • Audit and compliance
    • Responsible disclosure
    Documentation

    Getting Started

    • Introduction
    • How Gazebo works
    • Core concepts
    • Quickstart

    Agent Access

    • Access profiles
    • Bearer tokens
    • Audit logs

    MCP

    • Overview
    • Cursor
    • Claude Code
    • Windsurf
    • Any MCP client
    • Get credential reference

    Open Standard

    • Agent Consent Flow
    • Agent Identity Protocol (AIP) ↗

    REST API

    • Overview
    • Authentication
    • Services
    • Agents
    • Access policies
    • Audit events
    • Consent administration
    • Agent credential access
    • Errors and limits

    Security

    • Overview
    • Encryption model
    • Credential storage
    • Audit and compliance
    • Responsible disclosure
    DocsMCP

    MCP overview

    Gazebo exposes an MCP (Model Context Protocol) server that AI tools can connect to for credential retrieval. Any MCP-compatible client — Cursor, Claude Code, Windsurf, or a custom setup — can use the same endpoint.

    Endpoint

    https://app.gazebohq.com/api/mcp
    

    Authentication is via an agent bearer token passed as an Authorization header. Create the agent and its token at Agents; account API tokens and browser sessions cannot authenticate to this endpoint.

    Available tools

    get_identity

    Returns the calling agent's name and full access policy. Call this first to confirm which services are accessible before fetching credentials. No credentials are returned; nothing is logged.

    get_identity()
    → {
        status: "ok",
        agent_id: "...",
        name: "cursor-dev",
        accessible_services: [
          { service: "stripe", allowed_methods: ["GET", "POST"] },
          { service: "github", allowed_methods: ["GET"] }
        ]
      }
    

    get_credential

    Retrieves the credential for a named service. It requires service and method; key_name is optional and, when omitted, returns the service's primary credential. Credential-access attempts (including denials) are logged. The credential value is delivered to the MCP client/agent and must not be persisted.

    See the Get credential reference for full documentation.

    list_audit_events

    Returns recent credential-access attempts for the calling agent. Use limit from 1 through 50, and optionally filter with service and paginate with cursor. Every event includes a stable event_id for correlation.

    list_audit_events({ limit: 10, service: "stripe" })
    → {
        status: "ok",
        count: 3,
        events: [
          { event_id: "...", service: "stripe", method: "POST", outcome: "success", timestamp: "..." },
          { event_id: "...", service: "github", method: "GET", outcome: "denied", timestamp: "..." }
        ]
      }
    

    Recommended usage pattern

    1. get_identity()         → confirm which services are accessible
    2. get_credential(...)    → fetch the credential you need
    3. [use the credential]   → make your API call; do not persist the value
    4. list_audit_events(...) → optionally verify the access was logged
    

    Client setup

    • Cursor
    • Claude Code
    • Windsurf
    • Any MCP client

    Explore Gazebo

    Gazebo gives each agent an independent access boundary around your agent credentials, with controls for approval, auditing, and revocation.

    Scoped identities for AI agentsGive every agent only the credentials it needs.Credential security and audit controlsSee how access is protected, recorded, and revoked.
    Audit logsCursor
    Gazebo

    Credential management for AI agents. Scoped access, approval controls, and complete audit logs—without hardcoding or rotating shared API keys.

    Gazebo

    • Platform
    • Agent Consent Flow
    • Pricing
    • Status

    Explore

    • Services
    • Agents
    • Vaults

    Content

    • Writing
    • Topics
    • Blog
    • Docs
    • Spec

    Free Tools

    • Scanner

    Company

    • About
    • [email protected]
    • [email protected]

    © 2026 Gazebo. All rights reserved.

    PrivacyTermsSecurity