dot·sweep

Add dotsweep to your assistant

dotsweep is a remote MCP server, so any client that speaks MCP can call it. There is nothing to install and nothing to run: no account, no API key, no OAuth. The whole configuration is one URL — https://dotsweep.com/mcp.

Which of these am I?

If you are talking to Claude in a chat window — claude.ai, the desktop app, or the phone app — you want Claude connectors. Claude cannot add the server for you by being asked; adding a connector happens in your own settings, and no assistant has access to those.

If you have a terminal or an editor open, the command line and editor paths are one step each.

Claude — claude.ai or the desktop app

Do this part in a browser or the desktop app. The phone apps cannot add a connector; see below.

  1. Open Settings, then Connectors. Anthropic's help centre calls this path Customize → Connectors; both land in the same place.
  2. Click Add, then Add custom connector.
  3. Name it dotsweep.
  4. Paste the URL: https://dotsweep.com/mcp
  5. Click Add. Leave Advanced settings alone — that is for OAuth, and this server has none.
  6. 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.

Claude Code

One command, in your terminal:

claude mcp add --transport http dotsweep https://dotsweep.com/mcp

Here the transport is named, because this is a CLI flag rather than a settings screen. Add --scope user to have it in every project rather than the current one.

Codex

In ~/.codex/config.toml, or .codex/config.toml for a single project:

[mcp_servers.dotsweep]
url = "https://dotsweep.com/mcp"

Cursor, VS Code, Zed, Windsurf, Claude Desktop

These take the same object. One click, if the app is installed:

Add to Cursor Add to VS Code

Or paste it into the client's MCP config yourself:

{
  "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.

Any other client

It is streamable HTTP at https://dotsweep.com/mcp, 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 that has no MCP support at all — the answers come back as prose instead of tool calls.

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

Or just check a name here →

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.