EdgeOne Makers MCP for Claude Code: Setup & Config

What you can do with EdgeOne Makers in Claude Code

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.
• Select the China deployment variant instead of the international default.

Before you start: EdgeOne Makers in Claude Code

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

1. Choose Claude Code configuration scope

   For EdgeOne Makers MCP, open Project scope: .mcp.json at the repository root. Project JSON: merge into mcpServers; user scope: use the CLI.

2. Add EdgeOne Makers MCP to Claude Code

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

3. Check EdgeOne Makers MCP in Claude Code

   EdgeOne Makers MCP: Inspect claude mcp list and /mcp status.

{
  "mcpServers": {
    "edgeone-pages-mcp": {
      "type": "stdio",
      "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>"
      }
    }
  }
}

claude mcp add-json --scope project 'edgeone-pages-mcp' '{"type":"stdio","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 Code

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

deploy_folder_or_zip

For EdgeOne Makers's deploy_folder_or_zip, review the permission request and arguments in Claude Code before approval.

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

deploy_html

For EdgeOne Makers's deploy_html, review the permission request and arguments in Claude Code before approval.

EdgeOne Makers: full stored tool descriptions

Troubleshooting EdgeOne Makers in Claude Code

• If EdgeOne Makers MCP fails to start, check npx @edgeone/makers-mcp@latest (Node.js/npm), the working directory, and Claude Code's selected scope; inspect claude mcp list and /mcp.
• EdgeOne Makers MCP: check EDGEONE_PAGES_API_TOKEN, EDGEONE_PAGES_PROJECT_NAME; keep credentials out of shared .mcp.json.
• EdgeOne Makers MCP uses stdio here: Claude Code 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 Code troubleshooting lives in the /clients/claude-code guide.

Frequently asked questions