DomainPilot MCP Server

A Model Context Protocol (MCP) server that connects AI assistants to your Domain Pilot account. Manage domains, DNS records, uptime monitoring, SSL status, and more through natural language in Claude Desktop, Claude Code, or any MCP-compatible client.

Quick Start

The server is published on npm, so there's nothing to install or build -- npx fetches and runs it on demand.

1. Get your API token

Generate an MCP API token from your Domain Pilot settings page at domainpilot.io/settings/mcp.

2. Configure your AI client

Claude Code (recommended)

One command -- no config file to edit:

claude mcp add domainpilot --env DOMAINPILOT_API_TOKEN=your-token-here -- npx -y domainpilot-mcp

The -- separates Claude's flags from the command it runs; everything after it is the launch command. Pin a version with domainpilot-mcp@1.0.2 if you prefer.

Claude Desktop

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "domainpilot": {
      "command": "npx",
      "args": ["-y", "domainpilot-mcp"],
      "env": {
        "DOMAINPILOT_API_TOKEN": "your-token-here"
      }
    }
  }
}

ChatGPT (or other MCP clients)

Use the same pattern -- run npx -y domainpilot-mcp and set the DOMAINPILOT_API_TOKEN environment variable.

Running from source (development)

To run a local checkout instead of the published package:

git clone https://github.com/warunacds/domainpilot-mcp.git
cd domainpilot-mcp
npm install
npm run build

Then point your client's command/args at the built entry point -- "command": "node", "args": ["/absolute/path/to/domainpilot-mcp/dist/index.js"].

Remote HTTP development

The remote entrypoint serves stateless Streamable HTTP at /mcp:

# Development
npm run dev:http

# Built server
npm run build
npm run start:http

List tools without authentication:

curl http://localhost:3000/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Tool calls require a bearer token on the request:

curl http://localhost:3000/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -H 'Authorization: Bearer your-token-here' \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"list_domains","arguments":{}}}'

The HTTP entrypoint never uses DOMAINPILOT_API_TOKEN; each tool call uses only the bearer token supplied with that request.

Related MCP server: Coolify MCP Server

Available Tools

Note: DNS records can be added and updated, but deletion is intentionally not exposed through this server. Removing a record is the highest-risk DNS operation and the hardest to undo, so it is left out by design. Delete records via the Domain Pilot web UI instead.

Environment Variables

Development

# Run in development mode (no build needed)
DOMAINPILOT_API_TOKEN=your-token npm run dev

# Build for production
npm run build

# Run the built server
DOMAINPILOT_API_TOKEN=your-token npm start

Troubleshooting

"DOMAINPILOT_API_TOKEN is required"

Make sure the DOMAINPILOT_API_TOKEN environment variable is set in your MCP client configuration. Generate a token at your Domain Pilot settings page.

"Your Domain Pilot API token is invalid or expired"

Your token may have been revoked or expired. Generate a new one from your Domain Pilot settings page.

"Resource not found"

Double-check the domain name. It must match exactly as shown in your Domain Pilot account (e.g., example.com, not www.example.com or https://example.com).

Server not appearing in Claude Desktop

1. Make sure the path to dist/index.js is absolute (not relative)

2. Restart Claude Desktop after editing the config

3. Check that node is available in your PATH

Connection issues

If using a custom DOMAINPILOT_API_URL, verify the URL is correct and the server is reachable. The default URL points to the production Domain Pilot API.

License

MIT