Run the bridge and connect DevPilot to AI agents.

1. Start the MCP bridge

npx @littleee/devpilot-mcp server

This command starts the local HTTP bridge and the MCP server in one process.

2. Understand port behavior

• Default startup begins with port 5213.
• If 5213 is occupied and you did not pass --port, DevPilot MCP automatically falls back to the next available port.
• If you explicitly pass --port and it is occupied, the server stops with a clear error instead of silently switching ports.

3. Connect DevPilot in the browser

mountDevPilot({
  endpoint: "http://localhost:5213",
  features: {
    mcp: true,
    stability: true,
  },
});

In connected mode, DevPilot can sync sessions, send SSE updates, and route stability or repair workflows through the bridge.

4. Connect Claude, Codex, or another agent

Point your coding agent to the DevPilot MCP server, then let it inspect sessions, read pending annotations, or work through repair requests.

npx @littleee/devpilot-mcp server --mcp-only --http-url http://localhost:5213

To register DevPilot MCP globally in Claude Code, add it with user scope:

claude mcp add --scope user devpilot-mcp -- npx @littleee/devpilot-mcp server --mcp-only --http-url http://localhost:5213

Claude does not discover DevPilot automatically. The command above writes a global MCP entry for Claude on this machine. If your bridge falls back to another port, replace 5213 with the actual port.

5. Add MCP manually

If you prefer to maintain Claude MCP entries yourself, add a server entry like this to your MCP config:

{
  "mcpServers": {
    "devpilot": {
      "command": "npx",
      "args": ["-y", "@littleee/devpilot-mcp", "server"]
    }
  }
}

This starts both the local HTTP bridge and the stdio MCP server in one command. It uses port 5213 first and falls back automatically if you did not explicitly pass --port.