Cursor | Help

Cursor can use the 101domain MCP Server via a local mcp-remote bridge. This page shows how to point Cursor’s MCP settings (or ~/.cursor/mcp.json) at https://mcp.101domain.com, and includes a ready‑to‑paste example that keeps your 101domain API key in an environment variable so it never appears directly in your command line or config.

As of v0.48.0, Cursor supports unauthenticated HTTP servers natively. For token-authenticated servers like 101domain, you still need to use mcp-remote via the command server approach.

Configuration

Edit ~/.cursor/mcp.json or use Settings → MCP → Add server:

{
  "mcpServers": {
    "101domain": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@0.1.38",
        "https://mcp.101domain.com",
        "--silent"
      ],
      "env": {
        "AUTH_TOKEN": "your-api-key-here"
      }
    }
  }
}

Windows users: Replace "command": "npx" with "command": "cmd" and add "/c" as the first item in args. This is required because Windows cannot resolve npx (a .cmd script) without the system shell.

Cursor bug: Always use the env block for the token — never inline in --header.