Dashpilot MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add dashpilot-mcp -- uvx dashpilot-mcp

{
  "mcpServers": {
    "dashpilot-mcp": {
      "args": [
        "dashpilot-mcp"
      ],
      "command": "uvx"
    }
  }
}

[mcp_servers.dashpilot-mcp]
command = "uvx"
args = ["dashpilot-mcp"]

{
  "mcpServers": {
    "dashpilot-mcp": {
      "args": [
        "dashpilot-mcp"
      ],
      "command": "uvx"
    }
  }
}

{
  "mcpServers": {
    "dashpilot-mcp": {
      "args": [
        "dashpilot-mcp"
      ],
      "command": "uvx"
    }
  }
}

This one needs environment variables set before it will start: DASHPILOT_API_URL (DashPilot Cloud service endpoint — defaults to the hosted instance; set only for local development), DASHPILOT_API_KEY (Install key issued by DashPilot Cloud when you register the install), DASHPILOT_DRIVE_DEVELOPER_ID (Developer ID from the DoorDash Developer Portal (sandbox keys work out of the box)), DASHPILOT_DRIVE_KEY_ID (Key ID from the DoorDash Developer Portal), DASHPILOT_DRIVE_KEY (Drive signing secret from the DoorDash Developer Portal — used only on this machine to sign short-lived JWTs), DASHPILOT_DRIVE_ROUTING (managed (default) or manual — whether the config's routing block may switch this install between DoorDash's own sandbox and production hosts). The author declared them in the registry entry; get the values from the project itself.