Connect to DailyTube MCP

The DailyTube API speaks the Model Context Protocol (MCP) — AI agents like Claude and Cursor can connect to your account directly, with the same operations, permissions, and limits as the REST API.

How connecting works

One command adds DailyTube to your assistant; you sign in and approve access in your browser once. That's the whole setup.

• Server URL — https://api.daily-tube.com/v1/mcp (Streamable HTTP, remote server).
• Authentication — OAuth for MCP clients, or an API key for clients that only speak Bearer headers.
• Consent — you review each application once; revoke any time from the console's MCP page.

Claude Code

Run this in your terminal:

claude mcp add --transport http dailytube https://api.daily-tube.com/v1/mcp

Then, inside Claude Code, type /mcp, choose DailyTube, and select Authenticate. Your browser opens a DailyTube sign-in page — review the request and select Continue. The client keeps its own tokens and refreshes them.

Applications you authorize appear under Connected applications on the console's MCP page, where you can disconnect any of them at any time.

Other MCP clients

Add the server URL to your client and follow its sign-in flow. Clients that take JSON configuration start with:

{
  "mcpServers": {
    "dailytube": {
      "url": "https://api.daily-tube.com/v1/mcp"
    }
  }
}

Client setup varies; if yours can't connect to remote OAuth servers, use an API key below.

API key

Clients that don't support OAuth can use an API key as a Bearer credential:

Authorization: Bearer dtk_YOUR_KEY

Create a key on the API Keys page and give the agent its own key so you can revoke it independently. See Authentication for how keys work.

If something goes wrong

• Authentication fails or access expires — remove DailyTube from your client and add it again; you'll sign in and re-approve access.
• Account tools refuse calls — account operations need a plan with API access. The documentation tools work on every signed-in account.
• Your client isn't listed — check that it supports remote HTTP MCP servers and OAuth, then follow its custom-server instructions using the URL above. Clients without OAuth can use the API-key alternative. See Help if you need assistance.

What agents can do

Tools mirror the REST surfaces:

• Summaries — list, read, share, save, and trigger summaries
• Summarize — request new summaries from URLs or your feeds
• Chat — read and continue DailyTube chat threads
• Feeds & Channels — manage the sources and destinations your account uses
• Settings & Subscription — read and update your account's settings and plan information
• Help center — read and reply to your support tickets and feature requests

Account operations require a plan with API access, exactly like the REST API.

Documentation tools

Two additional tools let agents use this documentation:

• search_docs — full-text search across these docs and DailyTube's public articles. Returns ranked results with links; near-misses come back as clearly labeled suggestions.
• read_doc — fetch a document's content by the identifier search_docs returns, with pagination for long pages.

Documentation tools are available on every plan — they only require a signed-in account.

Limits

Tool calls count against the same budget as REST: by default, one call per 3 seconds and 500 per hour. API-key calls use that key's budget; OAuth calls share a budget for the user across authorized applications. Documentation-tool calls count too. See Rate limits.

Excess calls are rejected rather than silently queued. REST uses HTTP 429 and Retry-After; MCP tool errors use isError: true with the same machine-readable error code and retry_after seconds in the text payload. Clients decide when to retry; the server does not automatically wait or replay tool operations.

Authenticated tool operations appear in your Usage Logs with their credential identity. Protocol initialization and tool listing are not account-tool executions.

Errors

Account-tool failures preserve the API's machine-readable error identifiers — see Errors. Missing or invalid authentication is rejected; valid credentials do not bypass your plan or ownership checks.

Disconnecting an application removes its OAuth authorization and prevents refresh. Already-issued access tokens may remain usable until expiry; disconnect does not end your browser session or revoke API keys. Reconnect from the MCP client when fresh authorization is required. Global sign-out from the main app ends browser and OAuth refresh sessions; API keys remain separate.