Skip to content
The Daily Workflow logo

The Daily Workflow MCP server

Which MCP servers are The Daily Workflow's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-11-01

← Back to The Daily Workflow

Whose server it is
  • Registry namecom.thedailyworkflow/thedailyworkflow-mcpverified in the MCP registry

The registry name sits under thedailyworkflow.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-11-01
  • Stateanswerschecked 2026-11-01
  • Tools19
  • Server calls itselfthedailyworkflow-mcp
  • Server version1.27.0
  • Protocol version2025-06-18

On 2026-11-01 the server answered initialize and tools/list without a sign-in. First answer in 147 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • Parameters are untyped or undescribed in 16 of 19 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-11-01
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer290 ms
  • Space in an agent's context≈ 4,620 tokensthe definitions of all its tools (19), which an agent carries on every turn
  • Tool definitionsC · 69 of 100
  • Typed results0 of 19 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 16 of 19
  • Not saying whether it only reads or can destroy: 19 of 19

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers19 tools · read 2026-11-01
  • find_free_alternative

    Find verified free open-source replacements for a paid AI product. Backed by the Swap Map at thedailyworkflow.com/alternatives — every replacement is checked by hand against live GitHub (stars, license, last push). Answer honestly from…

  • search_mcp_servers

    Search the catalog of 3500+ MCP servers at thedailyworkflow.com. Args: query: Free-text search (matches name, description, keywords). Example: "notion", "postgres database". category: Filter by category. Common values: databases, web…

  • get_mcp_install_config

    Get a ready-to-paste install config for a specific MCP server and client. Args: slug: MCP server slug (from search_mcp_servers `slug` field). Example: "github-mcp". client: Target client. Values: claude-desktop, cursor, cline, windsurf…

  • get_mcp_details

    Get complete details for a specific MCP server: description, use cases, tools, install configs. Args: slug: MCP server slug. Returns: Full MCP record with description, long description, use_cases (list of scenarios), tools (what the…

  • list_mcp_categories

    List all MCP categories in the catalog with counts. Returns: Dict with `count` (total categories) and `categories` (list of {name, count}). Useful when the user wants to browse by category or asks "what kinds of MCP servers exist".

  • catalog_stats

    Stats about the MCP catalog at thedailyworkflow.com. Returns: total_servers (int), top_languages (list of {language, count}), catalog_url. Use this for context-setting questions like "how many MCP servers exist" or "what's the most…

  • search_ai_tools

    Search 15000+ AI tools in the thedailyworkflow.com catalog. Args: query: Free-text search (matches name, description, tags). Example: "image generation", "transcription", "chatbot". category: Filter by category. Examples: "Image…

  • get_ai_tool_details

    Full details for a specific AI tool: features, pricing, target audience, USP. Args: slug: Tool slug from search_ai_tools results (e.g. "chatgpt", "midjourney"). Returns: Dict with full description, key_features, pricing_details…

  • list_ai_tool_categories

    List all AI tool categories in the catalog with counts. Returns: Dict with `count` and `categories` (list of {name, count}). Useful when the user wants to browse tools by category.

  • search_pipelines

    Search 100+ ready-made AI workflow pipelines (step-by-step recipes). A pipeline is a complete plan: which AI tools to use in what order, with ready-to-paste prompts at each step, to accomplish a specific goal. Args: query: Free-text…

  • get_pipeline_details

    Full pipeline: title, goal, all steps with tools, instructions, prompts, pricing. Args: slug: Pipeline slug (from search_pipelines). lang: "en" or "ru" (default "en"). Returns: Dict with title, goal, steps (each: step number, title…

  • get_popular_pipelines

    Top-N most-used pipelines by hit count — what other users have found valuable. Args: lang: "en" or "ru" (default "en"). limit: Max results (1-25, default 10). Returns: Same shape as search_pipelines, sorted by hits descending. Use this…

  • build_custom_pipeline_url

    For a custom task (no existing pipeline matches), get a deep link to the Pipeline Builder on thedailyworkflow.com. The builder composes a step-by-step pipeline from 15000+ AI tools with ready-to-paste prompts. The MCP server doesn't run…

  • search_mcp_tutorials

    Search 147+ MCP tutorials covering install, configuration, comparison, build guides. Tutorials are curated step-by-step guides for installing and using MCP servers with specific clients (Claude Desktop, Cursor, Cline, Windsurf)…

  • get_tutorial_details

    Full tutorial content (markdown) with all steps, code blocks, screenshots. Args: slug: Tutorial slug (from search_mcp_tutorials). lang: en | ru. Default: en. Returns: Dict with title, summary, content (full markdown), difficulty…

  • search_qa_cases

    Search 147+ Q&A cases — curated solutions to real GitHub Issues with MCP servers and AI tools. Each case is structured as: problem (symptom) → cause → solution (markdown with code). Use this FIRST when the user reports an error or…

  • search_prompts

    Search 1700+ user-submitted AI prompts for ChatGPT, Claude, Midjourney, DALL-E, Cursor, Gemini and more. Each prompt is a copy-paste-ready template for a specific task (writing, coding, marketing, design, business, etc). Args: query…

  • get_my_saved_tools

    Return the saved AI tools ("My Workflow" stack) of the user who owns the given personal API key from thedailyworkflow.com. The user can generate the key on https://thedailyworkflow.com/my-workflow (section "Personal API key"). Ask the…

  • get_my_stack_health

    Health summary of the user's saved stack on thedailyworkflow.com: how many of their tools are alive, protected, slow or dead, and which ones are dead. Needs the personal API key (see get_my_saved_tools). Use this when the user asks…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "thedailyworkflow-mcp": {
      "type": "http",
      "url": "https://thedailyworkflow.com/api/v1/mcp/bridge"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http thedailyworkflow https://thedailyworkflow.com/api/v1/mcp/bridge

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://thedailyworkflow.com/api/v1/mcp/bridge as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.