hotlogin-mcp

MCP Server (stdio) for HotLogin Local API. npm package: hotlogin-local-api-mcp.

When using with Skills in the repository, see skills/xbrowser-automation/.

MCP

Cursor

Settings → MCP → Add new MCP server, example:

{
  "mcpServers": {
    "hotlogin-local-api": {
      "command": "npx",
      "args": ["-y", "hotlogin-local-api-mcp"],
      "env": {
        "PORT": "60000",
        "API_KEY": "your_api_key"
      }
    }
  }
}

If there is no authentication, you can remove env, or keep only PORT.

npx (minimal)

{
  "mcpServers": {
    "hotlogin-local-api": {
      "command": "npx",
      "args": ["-y", "hotlogin-local-api-mcp"]
    }
  }
}

Local Development (this repository)

npm install && npm run build

{
  "mcpServers": {
    "hotlogin-local-api": {
      "command": "node",
      "args": ["/你的路径/hotlogin-mcp/build/server.core.js"],
      "env": {
        "PORT": "60000",
        "API_KEY": "your_api_key"
      }
    }
  }
}

On Windows, if npx fails to start, you can change it to "command": "cmd", "args": ["/c", "npx", "-y", "hotlogin-local-api-mcp"].

Related MCP server: scout-mcp-server

Environment Variables

Consistent with src/api/config.ts:

Prerequisites

• HotLogin client is running, and Local API is accessible

• Node.js ≥ 18

Tools

Registered list: src/mcp/tools.ts, parameter validation: src/mcp/schemas.ts.

Typical workflow: env_create → env_launch (get wsEndpoint) → session_attach → page_visit / element_* → env_terminate.

Troubleshooting

• health_check failed: Verify that PORT / BASE_URL / API_KEY match the local service.

• session_attach failed or timed out: If wsEndpoint is expired, re-run env_launch; check local network/firewall.

License

MIT