This guide takes you from zero to retrieving a credential from Gazebo in about five minutes. We'll use Stripe as the example service.
Prerequisites
- A Gazebo account (sign up free)
- A Stripe API key (from your Stripe dashboard)
- An MCP-compatible AI tool (Cursor, Claude Code, or Windsurf) — or any HTTP client
Step 1: Connect Stripe
- Go to Settings → Services in the Gazebo dashboard
- Click Connect next to Stripe
- Paste your Stripe API key and click Save
Gazebo encrypts the key and stores it in the vault.
Step 2: Create an agent
- Go to Agents and click New agent
- Give it a name — e.g.
cursor-dev - Under Access, add Stripe with the methods your agent needs (e.g.
GETfor read-only) - Click Create
Step 3: Copy the bearer token
After creation, Gazebo shows your agent's bearer token. Copy it — you won't be able to see it again. If you lose it, regenerate it from the agent settings page.
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.
What just happened
- Your agent identified itself with the bearer token
- Gazebo checked its access profile — Stripe
GETis 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