Log inSubmit server
Edgeone Pages MCP logo

Edgeone Pages MCP

by TencentEdgeOne

Deploys static, built, and Next.js projects to EdgeOne Pages and returns a public deployment URL.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Edgeone Pages MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "tencentedgeone-edgeone-pages-mcp": {
      "command": "npx",
      "args": [
        "@edgeone/makers-mcp@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx @edgeone/makers-mcp@latest

initialize succeeded but no response to tools/list.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 27d ago.

Overview

TencentEdgeOne/edgeone-pages-mcp MCP server deploys web projects to EdgeOne Pages and returns a publicly accessible URL. Its `deploy_folder` tool accepts built assets, simple HTML/CSS/JS projects, and Next.js full-stack projects. The `account_info` tool reports the current EdgeOne Makers login state and account details. Use it when an agent needs to publish a local project through EdgeOne rather than another hosting provider.

Use cases

  • Deploy a static HTML, CSS, and JavaScript site
  • Publish Vite or Webpack build output
  • Release a Next.js full-stack project
  • Check the active EdgeOne Makers account

Key features

  • Deploys folders to EdgeOne Pages
  • Supports static and built web projects
  • Supports Next.js full-stack projects
  • Returns deployment URLs and project metadata
  • Reports EdgeOne account information
  • Supports browser login or API-token authentication

Tools2

What Edgeone Pages MCP lets your agent do. Expand a tool for its parameters.

Verified live~909 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

19/20 checks healthy over the last 78d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 11d ago via OSV.dev · @edgeone/makers-mcp@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars440Stargazers on the source repository.
npm downloads288Package downloads in the last 30 days.
Last commit3mo agoMost recent push to the default branch.
Install checkInconclusiveStarted but did not complete the MCP handshake in our test.
Tools exposed2Callable tools this server registers over MCP.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Edgeone Pages MCP works

What TencentEdgeOne/edgeone-pages-mcp MCP server does

TencentEdgeOne/edgeone-pages-mcp MCP server exposes EdgeOne Pages deployment through MCP. It is intended for projects that already exist in a local folder and need to be published as a publicly reachable site. The primary deployment operation is deploy_folder, which returns both a deployment URL and project metadata.

The accepted project types cover ordinary static sites, output generated by common build systems, and Next.js applications with full-stack behavior. A static project can contain HTML, CSS, and JavaScript files. A built project can contain the output produced by tools such as Vite or Webpack. The material also identifies Next.js full-stack projects as supported.

How it works

An MCP client starts the server with Node.js and invokes its deployment tool with a folder and a meaningful project name. The project name should describe the application or site, such as a blog, task application, or chat demo. It should not be generated from a date or an arbitrary random value.

Authentication can use the interactive browser flow or an API token. If the user is not authenticated, the browser login process starts automatically. After a successful deployment, the returned URL should be presented exactly as supplied, including any query parameters. The URL should be opened in the user’s regular system browser, not an embedded browser view, because the embedded view cannot handle the required SSO redirects.

Setup and configuration

TencentEdgeOne/edgeone-pages-mcp MCP server requires Node.js 18 or newer. A local MCP configuration can run the published package with npx @edgeone/makers-mcp@latest and a timeout of 600 seconds. The default configuration targets Tencent Cloud International. A China-region configuration adds the --region china argument.

EDGEONE_PAGES_API_TOKEN is optional. When supplied, it avoids the browser login flow; the README points to EdgeOne’s API-token documentation for obtaining one. EDGEONE_PAGES_PROJECT_NAME is also optional and skips the browser project-selection flow when set. Neither variable is needed when the corresponding interactive flow is acceptable.

For a quick single-page HTML preview, the material provides a hosted Streaming HTTP MCP endpoint at https://mcp-on-edge.edgeone.site/mcp-server, so local installation is not required for that path. The referenced source repository for this hosted option is TencentEdgeOne/self-hosted-pages-mcp.

Tools and capabilities

  • deploy_folder: Publishes a folder containing web assets to EdgeOne Pages. It supports built project output, simple static files, and Next.js full-stack projects, then returns the deployment URL and project metadata.
  • account_info: Reports the current EdgeOne Makers login status, account name, account ID, and login type.

The account tool is suited to requests about the active login or EdgeOne account. The deployment tool is the only deployment method described for this server.

Limitations and notes

If deployment fails, the failure should be reported rather than redirected to another deployment tool.

Do not treat a local HTML file opened with the file:// protocol as the deployment preview. Likewise, do not alter, shorten, or remove parts of the returned deployment URL. Query parameters may be required for access. The documentation does not list specific MCP desktop clients as supported, so client compatibility should be checked against the client’s MCP configuration support.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Edgeone Pages MCP

Install Node.js 18 or newer, then configure an MCP client to run `npx @edgeone/makers-mcp@latest` with a 600-second timeout.

Use the `deploy_folder` tool with the project folder and a descriptive project name. It supports static files, build output, and Next.js full-stack projects.

No. `EDGEONE_PAGES_API_TOKEN` is optional; without it, the server can use the browser login flow.

Call `account_info` to receive the current login status, account name, account ID, and login type.

Related MCP servers

All in Cloud Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewEdgeone Pages MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/tencentedgeone-edgeone-pages-mcp?style=directory)](https://allmcps.com/mcp/tencentedgeone-edgeone-pages-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/tencentedgeone-edgeone-pages-mcp"><img src="https://allmcps.com/api/badge/tencentedgeone-edgeone-pages-mcp?style=directory" alt="Edgeone Pages MCP on AllMCPs" /></a>