EdgeOne Makers MCP for VS Code: Setup & Config

What you can do with EdgeOne Makers in VS 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.
• Use a saved token and project name to avoid the two browser selection steps.

Before you start: EdgeOne Makers in VS 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 VS Code configuration

1. Choose VS Code configuration scope

   For EdgeOne Makers MCP, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

2. Add EdgeOne Makers MCP to VS Code

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

3. Check EdgeOne Makers MCP in VS Code

   EdgeOne Makers MCP: Start in VS Code’s MCP controls; inspect output and trust prompts.

{
  "servers": {
    "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 VS Code

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

deploy_folder_or_zip

Look for deploy_folder_or_zip among VS Code's agent-mode tools after starting EdgeOne Makers through the MCP controls.

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

deploy_html

Look for deploy_html among VS Code's agent-mode tools after starting EdgeOne Makers through the MCP controls.

EdgeOne Makers: full stored tool descriptions

Troubleshooting EdgeOne Makers in VS Code

• Make npx @edgeone/makers-mcp@latest (Node.js/npm) available in the workspace, container, or remote environment hosting EdgeOne Makers MCP. Start through VS Code's MCP controls; inspect output and trust prompts.
• For EdgeOne Makers MCP, keep EDGEONE_PAGES_API_TOKEN, EDGEONE_PAGES_PROJECT_NAME out of version control; VS Code documents input variables and secret handling.
• EdgeOne Makers MCP uses stdio here: VS 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 VS Code troubleshooting lives in the /clients/vscode guide.

Frequently asked questions