dot·sweep

Add dotsweep to any MCP client

Windsurf, Zed, Claude Desktop and the rest take the same object. There is no account, no API key and no OAuth, so the URL is the whole configuration.

{
  "mcpServers": {
    "dotsweep": { "type": "http", "url": "https://dotsweep.com/mcp" }
  }
}

Some clients ask only for a URL. It is https://dotsweep.com/mcp, with no headers and no token.

It is streamable HTTP, unauthenticated, and it answers initialize, tools/list and tools/call. The full reference is at /docs, which is also the document to paste into a chat window with no MCP support at all — the answers come back as prose instead of tool calls.

The endpoint is https://dotsweep.com/mcp — one URL, no account, no API key and no OAuth. It is free, and nothing runs on your machine: your assistant calls this site over HTTPS.

When it does not work

What you seeWhat it means
"I can't run that command from here"A CLI command went into a chat window. Use the connector steps instead — that assistant has no shell and no access to your settings.
Nothing to tap in the phone appConnectors are added on the web. Add it at claude.ai in a browser and it syncs.
Added, but no tools appearSwitch it on in the conversation's tool menu. A new connector is off in existing chats.
"Could not connect"Check the URL ends in /mcp and is https. /health answers if the origin is up.
It answers, but still reaches for whoisSay so once: a raw whois reports a rate-limited registry as available, which is the answer that costs money. That is what this server exists to stop.

What to ask once it is added

Another client

All of them on one page →