Connect FetchFox to Claude web and Desktop
Use the same remote FetchFox connector in Claude web and Desktop. A FetchFox account and project key are required; Claude account or organization settings may also control connector access.
Add the remote connector
Open Customize → Connectors → Add custom connector. Organization accounts may require an owner to add it first. Enter FetchFox and https://mcp.fetchfox.net/mcp, then continue to authentication.
FetchFox 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 FetchFox credits.
Try one request
Enable FetchFox for the conversation and check that youtube_transcript is listed. Ask: “Use FetchFox 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 FetchFox credit. The language model’s own fees or plan limits are separate. Check FetchFox 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
External documentation checked October 11, 2026. Client interfaces and third-party capabilities can change.