Cursor

编辑 ~/.cursor/mcp.json（全局）或项目下的 .cursor/mcp.json，写入：

{
  "mcpServers": {
    "ulzx": {
      "url": "https://xcslink.com/api/mcp",
      "headers": {
        "Authorization": "Bearer {{TOKEN}}"
      }
    }
  }
}

保存后在 Cursor 设置的 MCP 页面确认 ulzx 已启用。其他支持在配置文件里写 url 与 headers 的客户端，格式相同。

Claude 桌面版（以及只支持本地命令的客户端）

这类客户端不能直接填写请求头，需要借助开源工具 mcp-remote 转接。电脑上需先安装 Node.js 18 或更高版本。

打开配置文件：Claude 桌面版菜单“设置 → 开发者 → 编辑配置”，或直接编辑

• macOS：~/Library/Application Support/Claude/claude_desktop_config.json
• Windows：%APPDATA%\Claude\claude_desktop_config.json

写入以下内容后，完全退出并重新打开 Claude 桌面版：

{
  "mcpServers": {
    "ulzx": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://xcslink.com/api/mcp",
        "--header", "Authorization:${AUTH_HEADER}",
        "--transport", "http-only"
      ],
      "env": {
        "AUTH_HEADER": "Bearer {{TOKEN}}"
      }
    }
  }
}

令牌放在 env 里、args 中不留空格，是为了避开 Windows 下参数里空格被拆开的问题。

其他支持远程 MCP 的客户端

在客户端的 MCP 服务器设置里按下表填写：

如果客户端只能填写本地命令，按“Claude 桌面版”页签的方式用 mcp-remote 转接。

Cursor

Edit ~/.cursor/mcp.json (global) or .cursor/mcp.json in a project:

{
  "mcpServers": {
    "ulzx": {
      "url": "https://xcslink.com/api/mcp",
      "headers": {
        "Authorization": "Bearer {{TOKEN}}"
      }
    }
  }
}

Save the file, then check that ulzx is enabled on Cursor's MCP settings page. Any other client that takes url and headers in a config file uses the same shape.

Claude Desktop (and clients that only run local commands)

These clients cannot send a custom request header, so put the open-source bridge mcp-remote in front. It needs Node.js 18 or later.

Open the config file via “Settings → Developer → Edit Config” in Claude Desktop, or edit it directly:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Add the block below, then quit Claude Desktop completely and reopen it:

{
  "mcpServers": {
    "ulzx": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://xcslink.com/api/mcp",
        "--header", "Authorization:${AUTH_HEADER}",
        "--transport", "http-only"
      ],
      "env": {
        "AUTH_HEADER": "Bearer {{TOKEN}}"
      }
    }
  }
}

The token sits in env and no argument contains a space, which keeps Windows from splitting the header apart.

Other clients with remote MCP support

Fill in the client's MCP server form like this:

If the client only takes a local command, bridge it with mcp-remote as shown in the Claude Desktop tab.