EdgeOne Pages MCP

What is EdgeOne Pages MCP about?

EdgeOne Pages MCP provides a rapid way to push static HTML content, entire directories, or zip packages to EdgeOne Pages. After deployment the service stores the assets in EdgeOne KV and returns a publicly accessible URL that is served from the edge.

How to use EdgeOne Pages MCP?

1. Install the MCP server (e.g., via npx edgeone-pages-mcp).
2. Configure optional environment variables:
   • EDGEONE_PAGES_API_TOKEN – your EdgeOne Pages API token.
   • EDGEONE_PAGES_PROJECT_NAME – existing project name to update, or leave empty to create a new project.
3. Use the MCP protocol tools (deploy_html, deploy_folder, deploy_zip) to send content to the server.
4. The server deploys the content to EdgeOne Pages, stores it in KV, and returns a public URL.

Key Features

• Standard MCP interface – works with any MCP‑compatible client.
• Supports HTML, folders, and zip files – flexible deployment options.
• Automatic KV storage – content is cached at the edge for low‑latency access.
• Public URL generation – each deployment receives a unique, instantly reachable URL.
• Optional project update – supply a project name to update an existing EdgeOne Pages site.

Use Cases

• Quickly preview generated web pages from LLMs.
• Deploy static documentation sites or marketing landing pages without a full CI/CD pipeline.
• Share prototype UI mockups with stakeholders via a single URL.
• Host single‑page applications or demos directly from edge storage.

FAQ

Q: Do I need an EdgeOne Pages account? A: Yes, an account and an API token are required for deployments. The token can be obtained from the EdgeOne Pages console.

Q: Can I deploy to an existing project? A: Provide the existing project name in EDGEONE_PAGES_PROJECT_NAME. The server will update that project instead of creating a new one.

Q: What Node.js version is required? A: Node.js 18 or higher.

Q: How is the public URL formed? A: After deployment the server queries the EdgeOne Pages API for the base URL of the project and appends the path to the stored asset.

Q: Is there a HTTP‑streamable version of the server? A: Yes, a Streamable HTTP MCP server can be used by pointing the url field to https://mcp-on-edge.edgeone.site/mcp-server.

EdgeOne Pages MCP

An MCP service for deploying HTML content, folder, and zip file to EdgeOne Pages and obtaining a publicly accessible URL.

Demo

Deploy HTML

Deploy Folder

Requirements

• Node.js 18 or higher

Configure MCP

stdio MCP Server

Suitable for most MCP applications

{
  "mcpServers": {
    "edgeone-pages-mcp-server": {
      "command": "npx",
      "args": ["edgeone-pages-mcp"],
      "env": {
        // Optional. If deploying a folder or zip file to an EdgeOne Pages project
        // provide your EdgeOne Pages API token.
        // How to obtain your API token: https://edgeone.ai/document/177158578324279296
        "EDGEONE_PAGES_API_TOKEN": "",
        // Optional. Leave empty to create a new EdgeOne Pages project.
        // Provide a project name to update an existing project.
        "EDGEONE_PAGES_PROJECT_NAME": ""
      }
    }
  }
}

Streamable HTTP MCP Server

Available in applications supporting Streamable HTTP MCP Server

{
  "mcpServers": {
    "edgeone-pages-mcp-server": {
      "url": "https://mcp-on-edge.edgeone.site/mcp-server"
    }
  }
}

Architecture

The architecture diagram illustrates the workflow:

1. Large Language Model generates HTML content
2. Content is sent to the EdgeOne Pages MCP Server
3. MCP Server deploys the content to EdgeOne Pages Edge Functions
4. Content is stored in EdgeOne KV Store for fast edge access
5. MCP Server returns a public URL
6. Users can access the deployed content via browser with fast edge delivery

Features

• MCP protocol for rapid deployment of HTML content to EdgeOne Pages
• Automatic generation of publicly accessible URLs

Implementation

This MCP service integrates with EdgeOne Pages Functions to deploy static HTML content. The implementation uses:

1. EdgeOne Pages Functions - A serverless computing platform that allows execution of JavaScript/TypeScript code at the edge.

2. Key Implementation Details :

   • Uses EdgeOne Pages KV store to store and serve the HTML content
   • Automatically generates a public URL for each deployment
   • Handles API errors with appropriate error messages

3. How it works :

   • The MCP server accepts HTML content through the deploy_html tool
   • It connects to EdgeOne Pages API to get the base URL
   • Deploys the HTML content using the EdgeOne Pages KV API
   • Returns a publicly accessible URL to the deployed content

4. Usage Example :

   • Provide HTML content to the MCP service
   • Receive a public URL that can be accessed immediately

For more information, see the EdgeOne Pages Functions documentation and EdgeOne Pages KV Storage Guide.

License

MIT