DailyDeck MCP server: connect Claude Code, Cursor and Codex to your tasks

Add the server once at user scope, so it is available in every repository rather than one checkout:

claude mcp add --transport http --scope user dailydeck https://www.dailydeck.ai/mcp

Start Claude Code, run /mcp, choose dailydeck and sign in. Your browser opens the DailyDeck sign-in; approve access and return to the terminal. Check the connection any time with claude mcp get dailydeck.

On an individual Pro or Max plan, open Customize, then Connectors, click + and choose Add custom connector. Name it DailyDeck and paste the server URL:

https://www.dailydeck.ai/mcp

On Team or Enterprise, an owner first adds DailyDeck under Organization settings, then Connectors, using Add, Custom, then Web. Members then open Customize, then Connectors, and choose Connect on DailyDeck.

Connect and approve the DailyDeck sign-in. Enable the connector for a conversation using +, then Connectors. The same connection works on the desktop app and on the web.

Add DailyDeck to ~/.cursor/mcp.json to make it available in every project, or to .cursor/mcp.json in one project:

{
  "mcpServers": {
    "dailydeck": {
      "url": "https://www.dailydeck.ai/mcp"
    }
  }
}

Cursor asks you to sign in the first time it connects. The server then appears under MCP in Cursor's settings.

Add the server to ~/.codex/config.toml:

[mcp_servers.dailydeck]
url = "https://www.dailydeck.ai/mcp"

Then sign in once from the terminal:

codex mcp login dailydeck

Any client that speaks Streamable HTTP and OAuth can connect with the server URL alone. The client discovers the authorization server from https://www.dailydeck.ai/.well-known/oauth-protected-resource/mcp and registers itself, so there is nothing to configure in DailyDeck first. A client that cannot run OAuth can send a personal access token instead, described below.

OAuth is the default and the one to use in an interactive client. It signs the client in as you, with the same access you have in the app. Disconnect a client any time under Settings, then AI Integrations.

Personal access tokens suit headless agents, scripts and anywhere you want a connection that can do less. Create one under Settings, then AI Integrations, then Access Tokens. Pick one workspace or all of them, choose its scopes, and copy it: it is shown only once. Tokens look like dd_pat_….

Sent as the only bearer credential to the MCP server, a token lists just the tools its scopes cover. A token holding only :read scopes is therefore a read-only connection that can see your deck but not change it:

claude mcp add --transport http --scope user dailydeck-readonly https://www.dailydeck.ai/mcp \
  --header "Authorization: Bearer ${DAILYDECK_READONLY_PAT}"

The same tokens authorize the REST API under https://www.dailydeck.ai/api/mcp:

# List in-progress tasks (needs tasks:read)
curl "https://www.dailydeck.ai/api/mcp/tasks?status=in_progress" \
  -H "Authorization: Bearer dd_pat_xxx_yyy"

# Create a task (needs tasks:write)
curl -X POST https://www.dailydeck.ai/api/mcp/tasks \
  -H "Authorization: Bearer dd_pat_xxx_yyy" \
  -H "Content-Type: application/json" \
  -d '{"title": "Review the deploy checklist", "priority": "high"}'

401 Unauthorized

The OAuth session expired or the token was revoked. Sign in again from the client (/mcp in Claude Code, codex mcp login dailydeck in Codex), or create a new token.

A tool is missing or reported as not found

On a token connection the tool list follows the token's scopes. Add the scope the tool needs, or use OAuth.

403 Forbidden on a task or project

The token is limited to one workspace and the item belongs to another, or the token lacks the scope for that action.

The client never opens a sign-in window

Check that the URL is exactly https://www.dailydeck.ai/mcp and that the client supports remote HTTP servers. Restart the client after changing its configuration.