Data as of

EdgeOne Makers MCP for Windsurf: Setup & Config

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

What you can do with EdgeOne Makers in Windsurf

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

  • Preview one generated HTML page through the hosted connection.
  • Select the China deployment variant instead of the international default.

Before you start: EdgeOne Makers in Windsurf

  • 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 Windsurf configuration

  1. Choose Windsurf configuration scope

    For EdgeOne Makers MCP, open macOS/Linux: ~/.codeium/windsurf/mcp_config.json Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json. Merge into mcpServers; remote endpoints use serverUrl.

  2. Add EdgeOne Makers MCP to Windsurf

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

  3. Check EdgeOne Makers MCP in Windsurf

    EdgeOne Makers MCP: Refresh MCP in Windsurf settings and inspect Cascade’s tools.

Config file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json

Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.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 Windsurf

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

deploy_folder_or_zip

After refreshing EdgeOne Makers in Windsurf settings, check Cascade's tool list for deploy_folder_or_zip.

deploy_html

After refreshing EdgeOne Makers in Windsurf settings, check Cascade's tool list for deploy_html.

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

EdgeOne Makers: full stored tool descriptions

Troubleshooting EdgeOne Makers in Windsurf

  • Check npx @edgeone/makers-mcp@latest (Node.js/npm) on the machine running Windsurf's MCP integration for EdgeOne Makers MCP; refresh MCP and inspect Cascade's tools.
  • Check EDGEONE_PAGES_API_TOKEN, EDGEONE_PAGES_PROJECT_NAME for EdgeOne Makers MCP; do not bypass a Windsurf permission error with a broad administrator token.
  • EdgeOne Makers MCP uses stdio here: Windsurf 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 Windsurf troubleshooting lives in the /clients/windsurf guide.

EdgeOne Makers MCP — details. Windsurf guide

Frequently asked questions

Windsurf reads EdgeOne Makers MCP under mcpServers in ~/.codeium/windsurf/mcp_config.json on macOS/Linux; Windows uses %USERPROFILE%\.codeium\windsurf\mcp_config.json.

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

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

Windsurf'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 Windsurf's connected tool list; the stored list is not a live check.

The README's browser flows handle login and project selection. A token skips the former, and a project name skips the latter.

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