Data as of

EdgeOne Makers MCP for Cursor: Setup & Config

Cursor: EdgeOne Makers MCP publishes full-stack projects and gives users a public address for the result.

What you can do with EdgeOne Makers in Cursor

Choose between public project deployment and a hosted single-page preview, with the distinction explicit.

  • Use a saved token and project name to avoid the two browser selection steps.
  • Select the China deployment variant instead of the international default.

Before you start: EdgeOne Makers in Cursor

  • Local package: Node.js version 18 or above

This launch uses the international configuration from the README, not the older package in config_hint. Both environment entries are optional. Append --region china for the documented regional alternative. The remote_url belongs to the separate single-HTML preview service and uses HTTP rather than this local stdio launch.

EdgeOne Makers Cursor configuration

  1. Choose Cursor configuration scope

    For EdgeOne Makers MCP, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

  2. Add EdgeOne Makers MCP to Cursor

    Use the edgeone-pages-mcp entry below in mcpServers. Keep EdgeOne Makers MCP's documented stdio connection fields and your other Cursor entries.

  3. Check EdgeOne Makers MCP in Cursor

    EdgeOne Makers MCP: Enable in Cursor’s MCP settings; inspect tools.

Config file · Project: .cursor/mcp.json

User: ~/.cursor/mcp.json

JSON
{
  "mcpServers": {
    "edgeone-pages-mcp": {
      "command": "npx",
      "args": [
        "@edgeone/makers-mcp@latest"
      ],
      "env": {
        "EDGEONE_PAGES_API_TOKEN": "<optional credential replacing browser login>",
        "EDGEONE_PAGES_PROJECT_NAME": "<optional project selection replacing the browser chooser>"
      }
    }
  }
}

EdgeOne Makers tools available to Cursor

EdgeOne Makers's stored tool list documents 2 tools; compare it with Cursor's connected tool list, because the stored list is not a live check.

deploy_folder_or_zip

Find deploy_folder_or_zip under EdgeOne Makers in Cursor's MCP settings; inspect its arguments when the agent requests a call.

deploy_html

Find deploy_html under EdgeOne Makers in Cursor's MCP settings; inspect its arguments when the agent requests a call.

The supplied Pages inventory describes publishing HTML and reporting its public address.

EdgeOne Makers: full stored tool descriptions

Troubleshooting EdgeOne Makers in Cursor

  • Cursor must find npx @edgeone/makers-mcp@latest (Node.js/npm) for EdgeOne Makers MCP. Enable the project/user entry in MCP settings and inspect its tools.
  • Review EDGEONE_PAGES_API_TOKEN, EDGEONE_PAGES_PROJECT_NAME for EdgeOne Makers MCP before sharing project .cursor/mcp.json; project scope travels with the repository.
  • EdgeOne Makers MCP uses stdio here: Cursor must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
  • Known limitation: Pages-era tool metadata and the Makers README describe differently named versions of the integration.
  • Known limitation: Not stated in the README: preview retention, quotas, or the hosted endpoint's authentication requirements.
  • General Cursor troubleshooting lives in the /clients/cursor guide.

EdgeOne Makers MCP — details. Cursor guide

Frequently asked questions

Cursor's EdgeOne Makers MCP entry belongs under mcpServers in .cursor/mcp.json (project) or ~/.cursor/mcp.json (user). Confirm the active scope in MCP settings.

Cursor's edgeone-pages-mcp example uses stdio.

EdgeOne Makers MCP's Cursor configuration invokes npx @edgeone/makers-mcp@latest (Node.js/npm).

Cursor's EdgeOne Makers MCP example references EDGEONE_PAGES_API_TOKEN, EDGEONE_PAGES_PROJECT_NAME. Check these names if startup or authentication fails; the example alone does not distinguish required from optional values.

EdgeOne Makers MCP's stored list contains 2 tools, including deploy_folder_or_zip, deploy_html. Compare those names with Cursor's connected tool list; the stored list is not a live check.

The supplied text presents that URL specifically for previewing a single HTML page; full-stack publication is described for Makers.

No. The China example keeps the same package and adds --region china to its arguments.