Add Gazebo to Claude Code as an MCP server so Claude can retrieve credentials from your vault during coding sessions.

Prerequisites

• A Gazebo account with at least one service connected
• An agent created in Gazebo with a bearer token

Configuration

Add Gazebo to your Claude Code MCP configuration. Claude Code reads MCP servers from ~/.claude/claude_desktop_config.json:

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

Replace <your-agent-token> with the token from your agent's page in the Gazebo dashboard.

Restart Claude Code after updating the config.

Verify the connection

Ask Claude to call get_identity:

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

Retrieve a credential

get_credential({ service: "github", method: "GET" })
→ "ghp_..."

Claude can now use this token for GitHub API calls — reading repos, listing issues, and so on — within the permitted methods.

Usage guidance for Claude

Claude works well with Gazebo when given context about what it's allowed to do. You can prompt it directly:

"Use the Gazebo MCP server to get my GitHub token, then list the open issues on my repo."

Claude will call get_identity to confirm access, then get_credential to retrieve the token, then use it for the GitHub API call.

Troubleshooting

MCP server not appearing — Restart Claude Code after editing claude_desktop_config.json. Check JSON syntax with a linter.

401 Unauthorized — Token is wrong or the agent was deleted. Check the Gazebo dashboard.

Denial on get_credential — The method you requested isn't in the agent's access profile. Update the profile in the Gazebo dashboard.