daily.dev

dev.dailyPublished by daily.devOfficial publisherv1.0.0Updated Oct 24, 2026

Developer news feeds, posts, bookmarks, tags and search from daily.dev

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

Remote daily.dev MCP server that gives an assistant access to developer news feeds, posts, bookmarks, tags and search.

What you can do
  • Browse developer news feeds and posts from daily.dev
  • Search posts and content by keyword
  • Look up and follow tags
  • Read and manage the user's bookmarks
When to use it
Useful when you want an assistant to pull in current developer news, find articles on a topic, or work with your daily.dev bookmarks and tags while researching or writing.
Requirements
A remote endpoint at api.daily.dev over streamable HTTP. Authentication is required: OAuth if the client supports it, otherwise an Authorization header with a Bearer personal access token from the daily.dev API settings page. No local runtime or environment variables.
Before you install
The server needs a personal access token or OAuth grant tied to your daily.dev account; treat the Authorization value as a secret. Bookmark-related actions may change data in your account. Requests and queries go to daily.dev's hosted service.

Installation

In SourceWeft

  1. Open daily.dev in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.daily%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "daily-dev": {
      "type": "http",
      "url": "https://api.daily.dev/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 30, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Daily integrations