Skip to content

Windsurf dev.to Developer Blogs & Programming Tutorials — buy per-query (devtowatch) data_session_query

How to: Windsurf dev.to Developer Blogs & Programming Tutorials — buy per-query (devtowatch) data_session_query

client:Windsurf transport:streamable-http tool:data_session_query

Add dev.to Developer Blogs & Programming Tutorials — buy per-query (devtowatch) to Windsurf

  1. 01

    Open ~/.codeium/windsurf/mcp_config.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "data-developer-blog-programming-tutorial-community": {
      "serverUrl": "https://a2awire.com/mcp/data/devtowatch-dev-to-developer-blog-tutorial-firehose-11f3ce/http"
    }
  }
}
  1. 02

    Save the file and restart Windsurf.

  2. 03

    Ask for something data_session_query does. Windsurf lists the server's tools on connect and calls data_session_query itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that dev.to Developer Blogs & Programming Tutorials — buy per-query (devtowatch)'s identifier in your config matches the one above exactly.

Global only — Windsurf has no per-project MCP config. Refresh Cascade after saving. Windsurf docs

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.