DailyTube Digest

Conecta tu asistente de IA a tu cuenta de DailyTube Digest. Lee y busca resúmenes diarios de los feeds que sigues —YouTube, X, Reddit y más—. Resume enlaces individuales, gestiona feeds y canales de entrega, y continúa las conversaciones con Max. Servidor HTTP remoto Streamable con inicio de sesión OAuth o autenticación mediante clave API.

Servidor MCP alojado

npx add-mcp 'https://api.dtdigest.com/v1/mcp'

Se instala en Claude Code, Codex, Cursor y más

Documentación

Connect to DailyTube MCP

Your summaries, feeds, and DailyTube account—right inside the AI assistant you already use.

TERMINAL

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

After running the command, open Claude Code and type /mcp. Choose dailytube, select Authenticate, then sign in and approve access in your browser.

Connection details

Server URL

https://api.dtdigest.com/v1/mcp

Transport: Streamable HTTP. If your assistant asks for the server URL directly, use this.

Get more out of DailyTube

Real sessions look like this:

Using another assistant?

Use a client that supports remote HTTP servers and OAuth. Add the server URL and sign in when prompted. If your client uses the mcpServers configuration format, start with:

MCP CONFIG

{ "mcpServers": { "dailytube": { "url": "https://api.dtdigest.com/v1/mcp" } } }

If your client only supports Bearer headers, give it its own API key — setup and revocation stay independent from OAuth. Stuck? Contact support and we'll set your client up.

https://api.dtdigest.com/v1/mcp

If sign-in fails — remove DailyTube from your client and add it again; you'll re-approve access. Content and write tools need an active plan with API access; account identity, subscription details, plan listings and documentation remain available to authenticated accounts without API entitlement.

Connection details & reference

The DailyTube API speaks the Model Context Protocol (MCP) — AI agents like Claude and Cursor can connect to your account directly, with the same permissions and limits as the REST API. Most operations are available over MCP; a few, such as subscription upgrades, remain on the REST API, CLI, and website.

DailyTube is also becoming an installable app inside ChatGPT and Claude. See Plugins.

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.dtdigest.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.dtdigest.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.dtdigest.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.
  • Gated tools refuse calls — content and write operations need an active plan with API access. Account identity, subscription details, plan listings, documentation and skills remain available to authenticated accounts without API entitlement.
  • 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

Available tool groups:

  • 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
  • Account & Subscription — see which account is connected (get_profile, read_account), read your plan and status (read_subscription), and browse the plan catalog (list_plans). These work on any authenticated account, including before API access
  • Settings — update your account's settings
  • Help center — read and reply to your support tickets and feature requests

Other account operations require an active plan with API access. Entitlement errors identify the connected account and include catalog-based plans or support guidance when available. These suggestions never execute a payment. Technical rate limits retain their retry information without an upgrade offer.

ChatGPT can use the authenticated get_profile tool to label the connected account. The account ID remains stable across requests; names and email are display fields, not identity keys. For browser availability, use the hosted custom-MCP connection flow supported by your ChatGPT account/workspace. Importing a ZIP that declares an MCP server can be marked Desktop only even when the endpoint is remote HTTPS.

OAuth authorization is checked against current consent on each request. Revoking a grant blocks subsequent requests; an already-in-flight operation cannot be retracted. Reconnect when authorization expires or is revoked.

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. Issued access tokens are rejected on subsequent API requests once the grant is revoked; an in-flight operation cannot be retracted. 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.