Add dotsweep to Claude
Four clicks in your own settings. No assistant can do this for you — a connector is written to your account, and nothing you paste into a chat can reach it.
Do this part in a browser or the desktop app. The phone apps cannot add a connector; see below.
- Open Settings, then Connectors. Anthropic's help centre calls this path Customize → Connectors; both land in the same place.
- Click Add, then Add custom connector.
- Name it
dotsweep. - Paste the URL:
https://dotsweep.com/mcp - Click Add. Leave Advanced settings alone — that is for OAuth, and this server has none.
- Open a new chat and switch dotsweep on in the tool menu. Tools from a custom connector start at Ask each time, so the first call asks permission.
Three things guides get wrong about this screen
There is no transport to choose. Nothing asks you to pick between SSE and Streamable HTTP. If an assistant tells you to set the transport under Advanced settings, it is describing a field that is not there.
It is not a paid feature. Custom connectors work on the free plan, which allows one of them. Pro and Max have no such limit. On Team and Enterprise an Owner adds it once under Organization settings → Connectors and members then connect individually.
Claude reaches this server from Anthropic's cloud, not from your computer. That is how remote connectors work generally, and it is worth knowing whoever runs a server sees the lookups. Ours are covered by what this one records: the extension, never the name you searched.
Claude on iPhone or Android
You cannot add a connector from the phone apps — they can use servers already added to your account, but the add-connector screen is web and desktop only. So add it once at claude.ai in a browser using the steps above, and it appears on your phone by itself.
This is the case that produced this page. Pasting a
claude mcp add command into the phone app cannot work: it is a
Claude Code command, the phone app has no shell, and no assistant can write to
your connector settings.
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 see | What it means |
|---|---|
| "I can't run that command from here" | A CLI command went into a chat window. Use the steps instead — that assistant has no shell and no access to your settings. |
| Nothing to tap in the phone app | Connectors are added on the web. Add it at claude.ai in a browser and it syncs. |
| Added, but no tools appear | Switch 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 whois | Say 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
- "Is acmeforge.com free? Check .io and .ai too."
- "What does .ai actually cost to own for two years?"
- "Here are twelve name ideas — which have a free .com?"
Another client
- Claude Code — one terminal command, or the skill instead of the server
- Cursor — one click, or the same JSON as every other editor
- VS Code — one click, or the same JSON as every other editor
- Codex — two lines in config.toml
- Any MCP client — Windsurf, Zed, Claude Desktop and anything else that speaks MCP
Menu names come from Anthropic's help centre, read 2026-07-30: Get started with custom connectors using remote MCP. Claude's own UI wording shifts occasionally; the URL never does.