dailydev-mcp

A zero-dependency MCP server for the daily.dev Public API - feeds, search, bookmarks, and profile management for any Model Context Protocol client.

dailydev-mcp gives AI agents (Claude, Cursor, OpenCode, and any other MCP client) direct, structured access to daily.dev: your personalized feed, trending posts, keyword and semantic search, bookmarks, and your profile and tech stack.

Your agent stops being limited by its training cutoff, and you can manage your daily.dev presence without opening the browser.

Why daily.dev for agents

LLMs have knowledge cutoffs. daily.dev aggregates articles from 2,000+ sources, validated by community engagement, with a structured taxonomy for precise discovery - so an agent can stay current, get diverse perspectives, and understand what the developer community actually cares about.

The daily.dev Public API is free to use with a personal access token. This server is a thin, correct, zero-dependency wrapper around it - built on Go's standard library only, shipped as a single static binary.

Tools (33)

Group	Tools
Profile	get_profile, update_profile, list_experiences, create_experience, update_experience, delete_experience
Tech stack	list_stack, add_stack_item, update_stack_item, remove_stack_item
Feeds	get_feed (for you / popular / discussed / by tag / by source), list_tags, list_custom_feeds, get_custom_feed_posts
Search	search_posts, search_tags, search_sources, recommend_articles (keyword or semantic; experimental endpoint)
Posts	get_post, get_post_comments
Bookmarks	list_bookmarks, search_bookmarks, add_bookmark, remove_bookmark, move_bookmark, list_bookmark_lists, create_bookmark_list, delete_bookmark_list
Feed filters	get_feed_filters, update_tag_filter, update_source_filter (global or per custom feed)
Notifications	get_notifications, mark_notifications_read

API responses are passed through as pretty-printed JSON, so the agent sees exactly what the API returns - including error responses.

Install

go install github.com/itokun99/dailydev-mcp@latest

Or build from source:

git clone https://github.com/itokun99/dailydev-mcp.git
cd dailydev-mcp
go build -o dailydev-mcp .

Setup

1. Create a personal access token at https://daily.dev/settings/api (free accounts included).
2. Export it:

export DAILY_DEV_TOKEN="dda_your_token_here"

On macOS you can keep it in the Keychain instead:

security add-generic-password -a "$USER" -s "daily-dev-api" -w "dda_your_token"
export DAILY_DEV_TOKEN=$(security find-generic-password -a "$USER" -s "daily-dev-api" -w 2>/dev/null)

Configure your MCP client

{
  "mcpServers": {
    "dailydev": {
      "command": "dailydev-mcp",
      "env": {
        "DAILY_DEV_TOKEN": "dda_your_token_here"
      }
    }
  }
}

Use the full path to the binary if it is not on PATH. The server speaks MCP over stdio (JSON-RPC 2.0, one message per line) and logs diagnostics to stderr only.

Usage examples

Once connected, just ask:

• "What's trending on daily.dev about Go this week?"
• "Search daily.dev for MCP server design patterns and summarize the top results."
• "Bookmark the top 3 posts from my For You feed."
• "Create a bookmark list called 'Research: Postgres' and move the Postgres posts into it."
• "Update my daily.dev bio and add Go to my stack."
• "Follow the golang and postgres tags, and block crypto."
• "Give me my weekly dev digest from my For You feed."

Rate limits and plans

• Free accounts: 200 requests per month.
• daily.dev Plus: 60 requests per minute, and a few features are Plus-only (for example, moving a bookmark between lists).
• The server surfaces the API's rate-limit and plan errors verbatim (401, 403, 404, 429) so your agent can explain exactly why a call failed.

Security

• The token is sent only to api.daily.dev and never logged.
• Never commit the token; use environment variables or your OS keychain.

Development

go build ./...
go test ./...
go vet ./...

DAILY_DEV_API_BASE overrides the API base URL (useful for tests or a local proxy).

Known API quirks

Observed against the daily.dev Public API v1.0.0 (2026-09). These are server-side behaviours - this MCP server passes them through verbatim:

• Some IANA timezones are rejected. PATCH /profile/ refuses zones like Asia/Jakarta, Asia/Singapore, Asia/Manila, and Asia/Makassar with invalid timezone, while Asia/Tokyo, Asia/Bangkok, and Asia/Novosibirsk are accepted - the API's validator list appears incomplete. If your zone is rejected, the API (not this server) is the cause.
• POST /profile/experiences/ can return HTTP 500 with an empty body for every payload shape, including the spec-minimal type/title/startedAt. It is a server-side failure; retry later.
• startedAt must be a full RFC 3339 date-time (2019-06-01T00:00:00.000Z); a plain date (2019-06-01) is rejected with must match format "date-time".
• Stack items carry their title under tool.title (not title), and adding a tool that already exists fails with Stack item already exists in your profile.

License

MIT - see LICENSE.