Connect an MCP client

DeployMill is its MCP tools. The dashboard you sign into is a window onto what your agent builds. The actual product is the tool surface at POST /mcp, and you reach it by pointing an MCP client at the server. This page covers the one-time setup for the common clients.

What you need

Everything you need is the MCP endpoint URL. It looks like https://<your-host>/mcp and is shown (with a copy button) at the top of your dashboard. Add that URL to any MCP-capable client below. The first time the client connects it runs an OAuth 2.0 sign-in in your browser. Approve it once and the client is issued a bearer token scoped to your workspace. There is no API key to copy around.

The endpoint speaks Streamable HTTP (a single POST /mcp). Any client that supports remote HTTP MCP servers with OAuth works. The clients below are just the ones with first-class setup.

Claude Code (CLI)

One command. Substitute your endpoint URL:

claude mcp add --transport http deploymill https://<your-host>/mcp

Then run /mcp inside Claude Code and pick deploymill to complete the OAuth sign-in. Verify with claude mcp list. It should show deploymill as connected. From then on, ask Claude to start_project and it drives everything through the tools.

Claude Desktop / Claude.ai

deploymill is a remote connector:

1. Open Settings → Connectors (Claude Desktop) or Settings → Connectors on claude.ai.
2. Click Add custom connector.
3. Paste your MCP endpoint URL (https://<your-host>/mcp) and save.
4. Claude opens the OAuth sign-in in your browser. Approve it. The connector shows as connected and its tools become available in chat.

Cursor

Add deploymill to your MCP config, either ~/.cursor/mcp.json (global) or .cursor/mcp.json in a project:

{
  "mcpServers": {
    "deploymill": {
      "url": "https://<your-host>/mcp"
    }
  }
}

Reopen Cursor's MCP settings. deploymill appears with a Login / authenticate prompt that runs the OAuth flow. Once green, the tools are live in Composer/chat.

Codex CLI

Codex connects through the mcp-remote bridge, which turns the remote HTTP endpoint into a local stdio server and handles the OAuth sign-in. Add to ~/.codex/config.toml:

[mcp_servers.deploymill]
command = "npx"
args = ["-y", "mcp-remote", "https://<your-host>/mcp"]

Restart Codex. The first call opens the browser sign-in. The deploymill tools are then available in your session.

VS Code (Copilot / MCP)

Add a server to .vscode/mcp.json in your workspace (or your user settings):

{
  "servers": {
    "deploymill": {
      "type": "http",
      "url": "https://<your-host>/mcp"
    }
  }
}

Start the server from the MCP view. VS Code prompts for the OAuth sign-in on first use.

Any other MCP client

The endpoint is a standard remote MCP server:

• Transport: Streamable HTTP (POST https://<your-host>/mcp)
• Auth: OAuth 2.0 + PKCE. The client discovers the authorization endpoints from the server and runs the browser sign-in itself. Every request carries Authorization: Bearer <token>, and the token scopes you to your own workspace, so you only ever see and touch your own apps.
• No static key: there is nothing to paste besides the URL. (Older clients without native remote-MCP support can bridge through a tool like mcp-remote, but that's rarely needed now.)

Once you're connected

Your client can discover everything else from the tools themselves:

• Fetch the deploymill://guides resource for the full index of guides, or call the search_docs tool to find one by keyword.
• deploymill://docs/getting-started: the shortest path from nothing to a live app (start_project → push_files → live URL).
• deploymill://docs/troubleshooting: when something goes wrong during setup.