1. Home
  2. EdgeOne Makers MCP
  3. EdgeOne Makers MCP for Claude Desktop: Setup & Config

Data as of

EdgeOne Makers MCP for Claude Desktop: Setup & Config

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

What you can do with EdgeOne Makers in Claude Desktop

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

  • Obtain a public address after deploying a full-stack project to Makers.
  • Preview one generated HTML page through the hosted connection.

Before you start: EdgeOne Makers in Claude Desktop

  • 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 Claude Desktop configuration

  1. Choose Claude Desktop configuration scope

    For EdgeOne Makers MCP, open macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json. Merge under mcpServers via Settings → Developer → Edit Config when available.

  2. Add EdgeOne Makers MCP to Claude Desktop

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

  3. Check EdgeOne Makers MCP in Claude Desktop

    EdgeOne Makers MCP: Fully quit and reopen Claude Desktop; check developer diagnostics.

Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_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 Claude Desktop

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

deploy_folder_or_zip

When Claude Desktop requests deploy_folder_or_zip from EdgeOne Makers, review the action before approving it.

The supplied Pages inventory describes publishing a built frontend folder or ZIP and returning project details plus a URL.

deploy_html

When Claude Desktop requests deploy_html from EdgeOne Makers, review the action before approving it.

EdgeOne Makers: full stored tool descriptions

Troubleshooting EdgeOne Makers in Claude Desktop

  • Fully quit and reopen Claude Desktop for EdgeOne Makers MCP. If npx @edgeone/makers-mcp@latest (Node.js/npm) is missing, check the desktop process's PATH, which may differ from your terminal.
  • In Claude Desktop's EdgeOne Makers MCP entry, check EDGEONE_PAGES_API_TOKEN, EDGEONE_PAGES_PROJECT_NAME. Keep secrets out of shared screenshots and repositories.
  • EdgeOne Makers MCP uses stdio here: Claude Desktop 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 Claude Desktop troubleshooting lives in the /clients/claude-desktop guide.

EdgeOne Makers MCP — details. Claude Desktop guide

Frequently asked questions

Claude Desktop loads EdgeOne Makers MCP from claude_desktop_config.json: ~/Library/Application Support/Claude/ on macOS, or %APPDATA%\Claude\ on Windows. Open it via Settings → Developer → Edit Config when available.

Claude Desktop's edgeone-pages-mcp example uses stdio.

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

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

The README uses @edgeone/makers-mcp@latest. The older Pages package remains in the structured hint, but is not the current documented launch.

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