DropTheHassle MCP server

Your AI puts your site online on a free link with HTTPS. Your own .com later. No token needed. DropTheHassle also does domains, hosting, DNS and email forwarding. This server lets your AI publish your site, check whether a name is free, and move a domain that is already on your account onto one of your sites. It can hand you a payment link on checkout.stripe.com. It cannot spend your money, and it cannot turn email on. Buying a domain, or turning on email forwarding, stays a click you make.

Package dropthehassle-mcp 0.4.2 in this repo (MIT, Node.js 18+). Registry name: io.github.bosmdavid-gif/dropthehassle.

Prices are written as €19 / $19. Contact: hello@dropthehassle.com.

deploy_site works without a token. The site goes live on a free link with HTTPS and the reply contains a claim link for the human. On the hosted endpoint, search_domain and whoami also work without a token.

Claude Code:

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

Cursor, Windsurf or any client that takes a remote mcp.json entry:

{
  "mcpServers": {
    "dropthehassle": {
      "url": "https://dropthehassle.com/mcp"
    }
  }
}

Add a token (below) when you want the AI to list your sites, update them or attach a domain that is already on your account.

1. On dropthehassle.com, open the menu (top right) and choose Connect your AI. Copy the token. It starts with dth_.
2. Paste it into the config for your editor below. Do not commit the token.

Optional: set DTH_API only if you need an API base other than https://dropthehassle.com/api/v1.

User scope, so it is available in every project:

claude mcp add --scope user dropthehassle --env DTH_TOKEN="dth_your-token-here" -- npx -y dropthehassle-mcp

Or a project .mcp.json (Claude Code expands ${DTH_TOKEN}):

{
  "mcpServers": {
    "dropthehassle": {
      "command": "npx",
      "args": ["-y", "dropthehassle-mcp"],
      "env": {
        "DTH_TOKEN": "${DTH_TOKEN}"
      }
    }
  }
}

Claude Code asks you to approve a project .mcp.json the first time you run claude in that folder.

The button installs a stdio server named dropthehassle that runs npx -y dropthehassle-mcp and reads DTH_TOKEN from your environment.

To add it by hand, put this in ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "dropthehassle": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "dropthehassle-mcp"],
      "env": {
        "DTH_TOKEN": "${env:DTH_TOKEN}"
      }
    }
  }
}

The repo root .mcp.json is the same block, for clients that detect an MCP server from the repository.

Cascade reads ~/.codeium/windsurf/mcp_config.json (Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json). Open it from the Cascade MCP panel. New Devin Local tabs keep secrets in the gitignored project file .devin/mcp_config.local.json. Both use the same shape:

{
  "mcpServers": {
    "dropthehassle": {
      "command": "npx",
      "args": ["-y", "dropthehassle-mcp"],
      "env": {
        "DTH_TOKEN": "dth_your-token-here"
      }
    }
  }
}

Restart Windsurf after saving so the agent reloads the server.

smithery.yaml is a stdio config. The install wizard asks for an optional dthToken and passes it as DTH_TOKEN to npx -y dropthehassle-mcp. Leave it empty to try deploy_site anonymously.

The same server is published at https://dropthehassle.com/mcp (streamable HTTP). A client mcp.json can point at that URL instead of running npx. Send the token as a Bearer header. Without the header, initialize, tools/list, deploy_site, search_domain and whoami still work; the other tools need the token.

{
  "mcpServers": {
    "dropthehassle": {
      "url": "https://dropthehassle.com/mcp",
      "headers": {
        "Authorization": "Bearer dth_your-token-here"
      }
    }
  }
}

Examples: "put the site in ./dist online", "is pocketlighthouse.com free?", "give me a payment link for that .com".

Operator tools are not in the list above. They are registered only when DTH_OPS=1 is set (DTH_OPERATOR=1 is the same switch), or when a whoami check at startup shows the token belongs to the ops account. A normal token does not see them, and a call by name is rejected as an unknown tool. The API still returns 404 for those routes unless the token is the ops owner.

{
  "mcpServers": {
    "dropthehassle": {
      "command": "npx",
      "args": ["-y", "dropthehassle-mcp"],
      "env": {
        "DTH_TOKEN": "dth_your-token-here"
      }
    }
  }
}

Paste the token in that file. Claude Desktop does not expand ${env:DTH_TOKEN}. Restart Claude after saving.