# TencentEdgeOne/edgeone-pages-mcp [Health: Active]

**Category:** ☁️ Cloud Platforms  
**Repository:** https://github.com/TencentEdgeOne/edgeone-pages-mcp  
**GitHub Stars:** 440  
**npm Downloads (last month):** 288  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/tencentedgeone-edgeone-pages-mcp

## Description
An MCP service for deploying HTML content to EdgeOne Pages and obtaining a publicly accessible URL.

## Tools
Capabilities this server exposes over MCP:

- **deploy_folder** — Deploy a folder containing web assets to EdgeOne Pages. Supports built projects (from build tools like Vite, Webpack, etc.), simple static file projects (HTML, CSS, JS files), and NextJS full-stack projects. Returns: deployment URL and project metadata.

IMPORTANT RULES:
1. This is the ONLY deployment method for EdgeOne Pages/Makers. Do NOT fallback to other deployment tools (cloudstudio, vercel, netlify, etc.) if this tool fails. Instead, report the error to the user and suggest fixes based on the error message.
2. The projectName parameter should be a meaningful name describing the project (e.g. "my-blog", "todo-app", "ai-chat-demo"). Do NOT use date-based directory names or random strings as project names. Generate a descriptive name based on the project's purpose or content.
3. After deployment succeeds, your response MUST start with: "🎉 部署成功，页面已上线至 EdgeOne Makers". Then display the "url" field from the response EXACTLY as-is, character for character. Do NOT modify, truncate, or strip any part of the URL (especially query parameters like ?eo_token=...&eo_time=...). Without the full query string the page returns 401. The URL must be shown as a complete clickable link — never shorten it, never show just the domain. Do NOT open local HTML files with file:// protocol as preview.
4. If the user is not logged in, a browser login page will open automatically. No need to ask about region — the login page handles site selection internally.
5. NEVER open the deployment URL in the built-in browser/webview. The built-in browser cannot handle SSO redirects (302). Always show the URL as a clickable text link for the user to open in their system browser manually.
- **account_info** — Get the current EdgeOne Makers login status and account information. Use when the user asks about their login status, account info, who they are logged in as, or wants to check their EdgeOne account. Returns account name, ID, and login type.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "edgeone-pages-mcp": {
    "command": "npx",
    "args": ["@edgeone/makers-mcp@latest"]
  }
}
```

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/tencentedgeone-edgeone-pages-mcp/readme_