Connect TubeCP to Claude & Cursor

TubeCP exposes a hosted MCP server over HTTPS with OAuth. Your AI client connects to one URL, runs a sign-in flow, and then calls tools such as research_youtube using your TubeCP account quota.

What you need

Item	Value
MCP server URL	`https://tubecp.vercel.app/api/mcp`
Authentication	OAuth — sign in with your TubeCP account when prompted
TubeCP account	Create one or sign in before connecting

Claude (claude.ai)

Open Settings → Connectors → Add custom connector.
Name: TubeCP
MCP server URL: https://tubecp.vercel.app/api/mcp
Click Continue.
Under Authentication, keep Sign in now selected. Claude should detect OAuth automatically.
Under OAuth client, keep Use Claude's published identity (recommended).
Click Add, complete the TubeCP sign-in flow, then enable the connector in chat.

ChatGPT

Enable Settings → Apps → Advanced → Developer mode.
Go to Settings → Connectors → Create.
Connector URL: https://tubecp.vercel.app/api/mcp
Choose OAuth authentication and complete sign-in when prompted.

Cursor

Open Cursor Settings → MCP or run:

claude mcp add tubecp --transport http https://tubecp.vercel.app/api/mcp

Cursor completes the OAuth flow in your browser after you add the server.

Claude Code (CLI)

claude mcp add tubecp --transport http https://tubecp.vercel.app/api/mcp

Run /mcp in Claude Code if you need to finish or refresh authentication.

Claude Desktop (mcp-remote fallback)

If your desktop build does not support remote OAuth connectors yet:

{
  "mcpServers": {
    "tubecp": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://tubecp.vercel.app/api/mcp", "--transport", "http-only"]
    }
  }
}

Available tools

Tool	Description
`search_youtube`	Search YouTube for candidate videos
`get_transcript`	Fetch captions for a video
`analyze_video`	Score whether a video discusses a topic
`research_youtube`	Full search → analyze → rank pipeline
`build_knowledge_base`	Transcribe, chunk, and embed ranked videos (paid)
`chat_with_knowledge_base`	RAG chat with citations (paid)

Troubleshooting

Symptom	Fix
Connector asks for an API key / request headers	Choose Sign in now (OAuth), not manual bearer tokens. TubeCP no longer requires copying `tcp_…` keys for normal client setup.
OAuth loop or sign-in fails	Make sure you have a TubeCP account and complete sign-in at /sign-in when redirected.
`Sign in required` / `AUTH_REQUIRED`	Redeploy the latest app — the MCP endpoint must use OAuth, not web-session auth.
Tools not visible	Restart the client and enable the TubeCP connector in the chat tools menu.

Endpoint URL is also shown on Account → Hosted MCP.