Server facts
EdgeOne Makers MCP
Project
- Author
- TencentEdgeOne
- Website
- pages.edgeone.ai/
- License
- MIT
- Category
- Cloud & DevOps
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 439
- Last commit
- Data as of
Tags
- App Deployment
- Edgeone
- Full Stack
- Public Previews
Overview
Choose the connection path according to what you want to publish. For a full-stack project, the README describes a local package that deploys to EdgeOne Makers and produces a publicly reachable address. For a quick preview of one HTML page, it points to a hosted MCP endpoint using Streaming HTTP. That second path requires no local package installation, and its source is linked as a separate project. The README does not describe these two options as interchangeable ways to expose every deployment capability, so the preview endpoint should be understood in its narrower single-page role.
The local setup runs on Node.js, with version 18 as the minimum. Its default configuration targets Tencent Cloud International; a region argument selects the China variant. Browser interaction can be reduced through two optional environment values. Providing an API token bypasses login in the browser, while supplying a project name avoids the browser-based project chooser. Naming needs care when reading the supplied material: the repository slug and structured inventory still refer to Pages, but the README now identifies Makers and launches @edgeone/makers-mcp@latest. The older inventory describes HTML publication plus a frontend-folder or ZIP deployment operation returning a link and project details. Those entries are included with their original data provenance rather than presented as a verified catalog of the newer package.
Install & configure
Requirements
- Local package: Node.js version 18 or above
npx @edgeone/makers-mcp@latestThis 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.
Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Use Settings → Developer → Edit Config when available. Do not assume a Linux configuration path; check the client documentation for your platform. Remote servers use the app’s connector flow when supported, not the local stdio file shown here. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"edgeone-pages-mcp": {
"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>"
}
}
}
}Config file · Project: .cursor/mcp.json
User: ~/.cursor/mcp.json
The project path is relative to the workspace root. The tilde denotes your user home directory. Use Cursor’s MCP settings to confirm which configuration and scope your installed version is reading. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"edgeone-pages-mcp": {
"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>"
}
}
}
}Config file · Workspace: .vscode/mcp.json
For user scope, use the “MCP: Open User Configuration” command if available. Do not guess a user configuration path across operating systems, profiles, containers, or remote workspaces; check the client documentation. Merge this example with existing settings; do not overwrite unrelated servers.
{
"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>"
}
}
}
}Config file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json
Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json
Open the MCP configuration through Windsurf’s settings when possible to confirm the active file. Paths can differ in managed or future releases; check the client documentation if this location is not present. Merge this example with existing settings; do not overwrite unrelated servers.
{
"mcpServers": {
"edgeone-pages-mcp": {
"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>"
}
}
}
}Config file · Project scope: .mcp.json at the repository root
The project file uses mcpServers. For user scope, use claude mcp add --scope user rather than assuming .mcp.json in your home directory is the user configuration. Check the client documentation for managed settings and storage details. Merge this example with existing settings; do not overwrite unrelated servers.
{
"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>"
}
}
}
}Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.
Tools
Source: repository tool metadata. Tool descriptions are a documented snapshot, not a live capability check.
| Tool | What it does |
|---|---|
| deploy_folder_or_zip | The supplied Pages inventory describes publishing a built frontend folder or ZIP and returning project details plus a URL. |
| deploy_html | The supplied Pages inventory describes publishing HTML and reporting its public address. |
Names, permissions, and defaults can change. Check the current upstream documentation before granting access.
Use cases
- Obtain a public address after deploying a full-stack project to Makers.
- Preview one generated HTML page through the hosted connection.
- Use a saved token and project name to avoid the two browser selection steps.
- Select the China deployment variant instead of the international default.
Strengths
- Offers a hosted route for small previews alongside the local project-deployment package.
- Accepts optional values that remove interactive login and project selection.
- Documents regional configuration rather than leaving the region implicit.
Limitations
- Pages-era tool metadata and the Makers README describe differently named versions of the integration.
- Not stated in the README: preview retention, quotas, or the hosted endpoint's authentication requirements.
Frequently asked questions
Independent listing, not an affiliation or security review. Grant the least access needed and verify the upstream instructions before running code.
