RELATED 01
EdgeOne Pages MCP
OFFICIAL SERVERPublishes HTML or a built site folder to Tencent EdgeOne Pages and returns a public URL
440GitHub stars
446/wknpm downloads
61popularity score
EdgeOne Makers MCP
Deploys a local web project folder to Tencent EdgeOne Makers/Pages and returns its public URL
Official · EdgeOne Pages TypeScript Local · stdio Cloud platformsDeveloper tools
23 popularity score ↓ 80/wk
Connect your client
Local (npm)
Add in one click
Opens the app, which asks before it adds the server.
Or add it by command or config
Claude CodeTerminal
claude mcp add edgeone-makers -- npx @edgeone/makers-mcp@latestClaude Desktopclaude_desktop_config.json
{
"mcpServers": {
"edgeone-makers": {
"command": "npx",
"args": [
"@edgeone/makers-mcp@latest"
]
}
}
}Cursor~/.cursor/mcp.json
{
"mcpServers": {
"edgeone-makers": {
"command": "npx",
"args": [
"@edgeone/makers-mcp@latest"
]
}
}
}VS Code.vscode/mcp.json
{
"servers": {
"edgeone-makers": {
"type": "stdio",
"command": "npx",
"args": [
"@edgeone/makers-mcp@latest"
]
}
}
}Codex~/.codex/config.toml
[mcp_servers.edgeone-makers]
command = "npx"
args = ["@edgeone/makers-mcp@latest"]Gemini CLITerminal
gemini mcp add --scope user edgeone-makers npx -- @edgeone/makers-mcp@latestSettings 3
EDGEONE_PAGES_API_TOKEN |
Optional: EdgeOne Pages API token; when set, the browser login is skipped. |
|---|---|
EDGEONE_PAGES_PROJECT_NAME |
Optional: Project name to deploy to instead of one generated from the workspace. |
EDGEONE_CLI_PACKAGE |
Optional: npm spec of the EdgeOne CLI fetched via npx when no suitable global edgeone is installed (default edgeone@1.6.17-beta.1). |
What it does
EdgeOne Makers MCP is Tencent EdgeOne's local server for publishing a project from your machine to EdgeOne Makers (EdgeOne Pages). Given the absolute path of a built output folder and of the project root, it uploads the files, creates or reuses a Pages project, and hands back the live address. It handles plain static files, the output of build tools such as Vite or Webpack, and Next.js full-stack projects, plus projects with functions, node-functions or edge-functions folders.
The server does not talk to the EdgeOne API itself: it drives the EdgeOne CLI (`edgeone`), using a global install when it is version 1.6.17-beta.1 or newer and otherwise fetching edgeone@1.6.17-beta.1 through npx (overridable with EDGEONE_CLI_PACKAGE). If you are not signed in, the first deploy opens a browser login page. The project name comes from the tool call, the EDGEONE_PAGES_PROJECT_NAME setting, a name cached for the same workspace, or the workspace folder name.
Version 0.0.4 registers two tools, `deploy_folder` and `account_info`, and accepts command-line flags the README does not list: `--region global|china`, `--project`, `--clear` (clears the saved config) and `--version`. The bundled code also reports usage events (tool, duration, result, OS, Node and client version, and your EdgeOne account IDs once known) to Tencent Cloud Log Service in Singapore or Nanjing, depending on region; no switch to turn this off appears in the code (unpkg dist/index.js, 0.0.4).
What it needs
| Runtime | Node.js 18+ |
|---|
Node.js 18 or newer with npx. An EdgeOne Makers/Pages account on Tencent Cloud International (default) or Tencent Cloud China (start with `--region china`). Either a browser to finish the one-time login or an EdgeOne Pages API token. The EdgeOne CLI 1.6.17-beta.1 or newer on PATH, or network access so the server can fetch it through npx on first use. The README sets a client timeout of 600 seconds, since deploys can take minutes.
Limits
Deploys only to EdgeOne Makers/Pages; it cannot list, delete or roll back deployments or manage domains. It needs a folder already on disk and built: it does not run your build. Full-stack support named in the tool is for Next.js. Deployment URLs carry an access token in their query string, and the tool's own instructions warn that the page returns 401 without the full URL and that an editor's built-in browser cannot follow its sign-in redirect. The public GitHub repository's code is still that of the older edgeone-pages-mcp package; the 0.0.4 source is only in the published npm bundle.
Who it suits
Suits developers who already host on, or want to try, Tencent EdgeOne and want an assistant to push a built site or Next.js app and get a shareable link from inside their editor. It writes to your EdgeOne account and runs locally with your files, so it fits a personal machine rather than shared automation. For a one-file HTML preview with nothing installed, its README points to the hosted EdgeOne endpoint at mcp-on-edge.edgeone.site, which only takes HTML. If you deploy to other hosts, or need to manage existing projects rather than publish new builds, pick a server for that platform.
Tools 2
deploy_folder- Uploads a built folder (static or Next.js full-stack) to EdgeOne Pages and returns the live URL and project details
account_info- Reports whether you are logged in to EdgeOne and the account name, ID and login type