# DotMoose MCP server

> Browse DotMoose hosting products, promotions and domain prices, get quotes, and start a checkout from your assistant.

- Listing: https://mcp.tc/i/dotmoose
- Connect: use the server's own URL `https://mcp.dotmoose.com/public/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: none
- Category: [Cloud & DevOps](https://mcp.tc/c/cloud-devops)
- Vendor: DotMoose
- Homepage: <https://dotmoose.com/>

## About

Connects to DotMoose, a Canadian hosting provider, and exposes its public catalog. You can list current products, get a recommendation for a workload, see active promotions, plan how to publish an app, check and quote domains, and get non-binding CAD quotes. A signup tool creates a checkout link on clients.dotmoose.com.

The server runs as a hosted streamable HTTP endpoint at https://mcp.dotmoose.com/public/mcp. No sign-in or API key is needed. It does not accept personal data, passwords, payment details or credentials. Account, billing and support tasks use a separate authenticated endpoint.

## What it can do

- List current public hosting products and offerings
- Recommend the smallest suitable product for a workload
- Show active curated promotion codes
- Plan a publication path for an app, API, bot or MCP server
- Check domain availability and quote registration, transfer or renewal
- Get short-lived non-binding CAD product quotes
- Create a checkout continuation link for signup

## Tools (8)

- `list_public_products`: List currently orderable public products plus a directory of domains, Dedicated quotes and other… (read-only)
- `recommend_product`: Recommend the smallest suitable public product set for a workload, or a Dedicated quote handoff. (read-only)
- `list_current_promotions`: List active promotion codes curated for public visibility, optionally by product or billing cycle. (read-only)
- `plan_app_publication`: Suggest a product and workflow for publishing a website, app, API, bot, MCP server or tool. (read-only)
- `quote_public_product`: Return a short-lived non-binding CAD quote for a public product. (read-only)
- `check_domain_availability`: Check whether a domain is available using the live lookup, without WHOIS contact data. (read-only)
- `quote_domain`: Return standard CAD TLD pricing for domain registration, transfer or renewal. (read-only)
- `start_signup`: Create a signed selection and a clients.dotmoose.com checkout continuation URL.

## Example prompts

- "Which DotMoose hosting plan fits a small WordPress site?"
- "Is example.ca available, and what does it cost to register for 2 years?"
- "What promotions are active for DotMoose VPS plans?"
- "Plan how to host a Dockerized Node API with a database on DotMoose."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http dotmoose https://mcp.dotmoose.com/public/mcp
```

2. Start Claude Code and type `/mcp`. **dotmoose** should show as connected.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **DotMoose** and paste this URL:

```url
https://mcp.dotmoose.com/public/mcp
```

3. Click **Add**. Its tools appear in the chat’s tools menu.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=DotMoose&connectorUrl=https%3A%2F%2Fmcp.dotmoose.com%2Fpublic%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://mcp.dotmoose.com/public/mcp` and click **Add**.

3. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://mcp.dotmoose.com/public/mcp` as the server URL, then for authentication choose **No authentication**.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=dotmoose&config=eyJ1cmwiOiJodHRwczovL21jcC5kb3Rtb29zZS5jb20vcHVibGljL21jcCJ9>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "dotmoose": {
      "url": "https://mcp.dotmoose.com/public/mcp"
    }
  }
}
```

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=dotmoose&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.dotmoose.com%2Fpublic%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"dotmoose","type":"http","url":"https://mcp.dotmoose.com/public/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "dotmoose": {
      "type": "http",
      "url": "https://mcp.dotmoose.com/public/mcp"
    }
  }
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "dotmoose": {
      "serverUrl": "https://mcp.dotmoose.com/public/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add dotmoose --url https://mcp.dotmoose.com/public/mcp
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.dotmoose]
url = "https://mcp.dotmoose.com/public/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http dotmoose https://mcp.dotmoose.com/public/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "dotmoose": {
      "type": "http",
      "url": "https://mcp.dotmoose.com/public/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.dotmoose.com/public/mcp`.

## Recent changes

- 2026-10-24 01:39 UTC: 7 tools changed. Source: automatic check. Changed: check\_domain\_availability, list\_current\_promotions, list\_public\_products, plan\_app\_publication, quote\_domain, quote\_public\_product, recommend\_product.
- 2026-10-23 07:24 UTC: Tracking started: 8 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/dotmoose#history (Atom feed: https://mcp.tc/i/dotmoose/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 0.2.0
- MCP protocol version: 2026-07-28
- Last checked: 2026-11-18 (reachable)
- Listed: 2026-10-23
- Updated: 2026-10-24

---
Source: https://mcp.tc/i/dotmoose (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
