# Connect SnipBob to Claude web and Desktop

Use the same remote SnipBob connector in Claude web and Desktop. A SnipBob account and project key are required; Claude account or organization settings may also control connector access.

Canonical: https://snipbob.com/integrations/claude

## Add the remote connector

Open Customize → Connectors → Add custom connector. Organization accounts may require an owner to add it first. Enter SnipBob and https://mcp.fetchfox.net/mcp, then continue to authentication.

SnipBob currently uses a fixed key, not OAuth. Select No sign in for OAuth authentication and add the request header Authorization with value Bearer YOUR_KEY. Save the connector. Keep this credential private; anyone given a shared connector key can spend its SnipBob credits.

## Try one request

Enable SnipBob for the conversation and check that youtube_transcript is listed. Ask: “Use SnipBob to retrieve the transcript for this public YouTube URL, then show three useful timestamps. Make only one tool call.” Review the URL before approving the call.

One successful transcript request uses one SnipBob credit. The language model’s own fees or plan limits are separate. Check SnipBob request history afterward. A captionless video may fail without a credit charge.

## Web connector versus local Desktop configuration

Remote connectors run through Claude’s cloud connection in both web and Desktop. They do not use claude_desktop_config.json. Local Desktop MCP servers are a different mechanism. If your interface lacks request-header authentication, use the supported Cursor or Claude Code instructions while checking your Claude account’s connector settings. Never put the key in the MCP URL.

## Sources

- [Claude remote connector setup and request headers](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp)

## Related pages

- https://snipbob.com/docs

- https://snipbob.com/integrations/cursor

- https://snipbob.com/guides/youtube-transcripts-for-rag