← Back to directory
E

EdgeOne Makers MCP Server

Official
MCP service for deploying HTML content to EdgeOne Makers and getting a public URL
Category
Cloud Storage #14 of 15
Stars
★ 437 Popular
Transport
stdio (local process) · Streamable HTTP
Runtime
Node.js 18+ · Hosted (no local runtime)
Credentials
Optional API key
License
MIT
Last commit
35FMRS · D

This server integrates EdgeOne Makers deployment into the MCP ecosystem, suitable for quick HTML deployments. It is easy to configure and supports multiple authentication methods, but security risks should be considered.

Strongest · Documentation 8/20 Weakest · Reliability 6/20

Reliability
6/20
Security and permissions
6/20
Maintenance
8/20
Documentation
8/20
Setup experience
7/20
Why each score
Reliability 6/20
The repository contains source code, but the README does not list tools or detailed behavior. No CI workflows or tests are present, so we cannot verify that the server starts cleanly and completes the MCP handshake. The server depends on an external service (EdgeOne) and error handling details are unclear. Therefore the score is capped at 12, but due to lack of execution evidence it is reduced to 6.
Security and permissions 6/20
The README recommends using environment variables for API tokens, but does not clarify the token's permission scope or data flow. The server prompts a browser login, but details on least privilege or confirmation of dangerous operations are missing. No obvious malicious code is found, but security practices are incomplete, hence 6. No red flags triggered.
Maintenance 8/20
This is an active repository with an MIT license, 430 stars, and a small number of open issues. However, from static reading we cannot confirm release history or dependency update frequency. There is no clear security response channel. Thus 8.
Documentation 8/20
The README provides clear installation and configuration examples, including two regional settings and optional environment variables. But it lacks tool parameters, limits, troubleshooting, and cost information. Source comments may help, but static reading is insufficient for full verification. Thus 8.
Setup experience 7/20
Setup is simple: use npx command with client config examples. However, it requires Node.js 18+ and may involve a browser login flow, adding complexity. No verifiable execution evidence is present, so per static calibration max is 15, but considering potential friction, we give 7.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkChanges third-party account data

Best for

  • Developers who need to quickly deploy HTML content to EdgeOne Makers and get a public URL
  • Users who want to integrate deployment into their MCP-driven workflows

Not for

  • Users who do not need EdgeOne Makers deployment
  • Users who cannot use Node.js environment

Required permissions

  • API token (optional) to skip login
  • Project name (optional) to select project
  • Browser login (optional)

Risks and side effects

  • API token leakage could lead to unauthorized deployments
  • Deployed content may be publicly accessible, so avoid exposing sensitive information

Setup

Before you start

Runtime:Node.js 18+ · Hosted (no local runtime)

EDGEONE_PAGES_API_TOKEN optionalsecret
Other optional settings (1)
EDGEONE_PAGES_PROJECT_NAME optional
  1. Ensure Node.js 18 or higher.
  2. Add the server configuration to your MCP client, using npx command like npx @edgeone/makers-mcp@latest, optionally setting environment variables EDGEONE_PAGES_API_TOKEN and EDGEONE_PAGES_PROJECT_NAME.
  3. For Tencent Cloud China, add --region china argument.
  4. Alternatively, use the remote streaming HTTP endpoint: url: https://mcp-on-edge.edgeone.site/mcp-server.

Check that it works

Add edgeone-makers-mcp-server to your client's MCP config and restart, then ask the AI to deploy a simple HTML page; receiving a publicly accessible URL proves the connection works.

Troubleshooting

  1. Check Node.js version is 18 or higher; ensure network connectivity; if using API token, verify it is valid; if using browser login, ensure you can access the login page.

Things to try

Once connected, you can ask your AI assistant things like:

  • Deploy my index.html to EdgeOne Makers and give me a public URL
  • With the --region china config, deploy the current project so it is publicly accessible
  • Use the remote HTTP endpoint to quickly preview my single-page HTML

Use cases

Quickly deploy a single HTML page for preview
Deploy full-stack projects to EdgeOne Makers and get a public URL

Overview

EdgeOne Makers MCP Server is an MCP service for deploying full-stack projects to EdgeOne Makers and obtaining publicly accessible URLs. It supports authentication via API token or browser login, and project selection can be configured via environment variables. Requires Node.js 18 or higher, and can be run via npx or a remote streaming HTTP endpoint.

Similar servers

Source revision ef1ab92e8e80 Data synced 2026-10-12 Read the FMRS scoring method