Quickstart

This guide takes you from zero to retrieving a credential from Gazebo in about five minutes. We'll use Stripe as the example service.

This is the manual agent-token path. To connect without copying a token, use the OAuth guides for Cursor, Claude Desktop or Devin: connect the service, add Gazebo's MCP URL, then approve selected keys. Use a fictional key for an initial integration test.

Prerequisites

• A Gazebo account (sign up free)
• A Stripe API key (from your Stripe dashboard)
• A remote HTTP MCP client that supports manual bearer headers, or an HTTP client

---

Step 1: Connect Stripe

1. Go to Settings → Services in the Gazebo dashboard
2. Click Connect next to Stripe
3. Paste your Stripe API key and click Save

Gazebo encrypts the key and stores it in the vault.

---

Step 2: Create an agent

1. Go to Agents and click New agent
2. Give it a name — e.g. cursor-dev
3. Under Access, add Stripe with the declared methods that may permit credential release (e.g. GET). Use a provider-enforced read-only key if the agent must not write.
4. Click Create

---

Step 3: Copy the bearer token

After creation, Gazebo shows your agent's bearer token. Store it securely—you won't be able to see it again. If lost, create a replacement agent and revoke the old one.

---

Step 4: Configure your MCP client

Add Gazebo to your MCP config. For Cursor, add to .cursor/mcp.json:

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

Replace <your-token> with the token from Step 3.

---

Step 5: Verify and retrieve

In Cursor (or your tool), call:

get_identity()

You should see your agent's name and the Stripe service in its access list.

Then retrieve the credential:

get_credential({ service: "stripe", method: "GET" })

Gazebo returns the plaintext Stripe API key. The agent can now use it to make Stripe API calls.

The calling runtime receives the key; trust that runtime and its host. Provider permissions govern subsequent Stripe calls. Revoking the Gazebo agent blocks new retrieval, not use of a key already retrieved. The audit log records retrieval, not later Stripe activity.

---

What just happened

• Your agent identified itself with the bearer token
• Gazebo checked its access profile — Stripe GET is permitted
• Gazebo logged the access and returned the credential
• The entire interaction is visible in your audit log

---

Next steps

• Access profiles — understand and refine what your agent can access
• Get credential reference — full tool reference including error handling
• Audit logs — see your access history