AI Assistants

Connect Claude Code and Other Clients

Add Domain Pilot to Claude Code from the terminal, or to any other MCP client

Claude Code connects to Domain Pilot with one command and a browser sign-in. The same server URL also works in any other MCP client that supports remote servers.

Before You Begin

  • A Domain Pilot account. Two-factor authentication (Settings → Security in Domain Pilot) is required once your sign-up grace period ends
  • Claude Code installed

Step 1: Add the Server

Run this in your terminal:

claude mcp add --transport http domainpilot \
  https://mcp.domainpilot.io/mcp

By default the server is added for the current project only. Add --scope user to make it available in every project:

claude mcp add --transport http --scope user domainpilot \
  https://mcp.domainpilot.io/mcp

Step 2: Sign In

  1. Start Claude Code and run /mcp
  2. Select domainpilot. It is marked as needing authentication
  3. Choose the authenticate option. Your browser opens the Domain Pilot sign-in page
  4. Sign in if needed, check that the page names Claude Code as the app asking for access, and click Approve

Back in the terminal, the server shows as connected with 15 tools. You can also sign in without opening the /mcp menu:

claude mcp login domainpilot

Step 3: Try It

Ask Claude Code something like "Show my Domain Pilot dashboard stats" or "List the DNS records for example.com". To check the connection at any time:

claude mcp list

Domain Pilot should show as Connected.

Disconnect

claude mcp remove domainpilot

This also deletes the stored sign-in. To keep the server but sign out, open /mcp and choose Clear authentication. Either way, you can also click Disconnect next to Claude Code under Settings → MCP in Domain Pilot to make sure access is revoked.

Other MCP Clients

Any client that supports remote MCP servers over HTTP works with the same URL: https://mcp.domainpilot.io/mcp. Sign-in with Domain Pilot works in Claude, ChatGPT, Claude Code and clients that return to a localhost address after sign-in. Clients that return to their own web address or app link, such as Cursor and VS Code, cannot sign in this way yet. Use a static token with them instead.

Clients That Only Send a Fixed Header

If your client cannot run a sign-in flow, use a static token instead:

  1. In Domain Pilot, go to Settings → MCP and click Generate Token. Two-factor authentication must be enabled
  2. Copy the token. It is shown only once
  3. Configure the client to send it as a bearer token on every request to https://mcp.domainpilot.io/mcp:
Authorization: Bearer your-token-here

In Claude Code, for example:

claude mcp add --transport http domainpilot https://mcp.domainpilot.io/mcp \
  --header "Authorization: Bearer your-token-here"

Static tokens do not expire on their own. Revoke one from the same settings page when you no longer need it.

Run the Server Locally

The server is also published on npm as domainpilot-mcp for clients that only support local, command-based servers. It needs a static token in the DOMAINPILOT_API_TOKEN environment variable:

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

See the domainpilot-mcp README for the config file format used by other clients.