---
title: "Claude Desktop MCP Setup | Gazebo Docs"
description: "Connect Claude Desktop to Gazebo using OAuth, approve selected service keys, verify identity and revoke future credential access."
url: "https://gazebohq.com/docs/mcp/claude-desktop"
---

Connect Claude Desktop to Gazebo through a remote custom connector. This is separate from [Claude Code](/docs/mcp/claude-code) and uses Anthropic's hosted connector infrastructure, not a local-only credential path.

## Connect

1. In Claude, open **Settings → Connectors** and add a custom connector.
2. Enter `https://app.gazebohq.com/api/mcp`.
3. Choose **Sign in now**, **Use Claude's published identity**, and **Streamable HTTP** where these options are shown.
4. Add the connector and connect. Sign in to Gazebo, select only the service keys to share, choose an access deadline and approve.

Do not choose **No sign-in**. No manually supplied client secret or agent-token header is needed for this flow. Custom-connector availability and controls depend on your Claude account and version; consult [Claude's current connector guide](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp).

## Verify

Start with:

> Use Gazebo's get_identity tool to show my connection and approved service keys. Do not retrieve any credential values.

For a first retrieval, use only a fictional test key. OAuth calls require the explicitly approved `key_name`:

```text
get_credential({ service: "your-test-service", key_name: "api_key", method: "GET" })
```

Claude may request tool approval separately from Gazebo's OAuth approval. Approve only the intended call. Ask it to report success without displaying or saving the value.

## Credential handling and revocation

The actual stored provider key is returned to the runtime; Anthropic's infrastructure and model context may receive it. A request not to display or save it is not a guarantee about host retention. Use provider-scoped credentials and trusted runtimes.

Revoke the connection in **Gazebo → Settings → Developer → Consent clients → Active Grants**. Leave the connector configured, make a fresh call and do not reconnect during the revocation check. New retrieval should require authorization again. Previously returned provider keys remain valid until invalidated at their provider.

## Tested path

**Tested with Claude Desktop on macOS.** See the [compatibility guide](https://github.com/gazebohq/gazebo-mcp/blob/main/docs/client-verification.md) for detailed results.