EdgeOne Pages MCP

What is EdgeOne Pages MCP?

EdgeOne Pages MCP is an MCP (Micro-Cloud Platform) service designed for deploying HTML content, folders, and zip files to EdgeOne Pages. It provides a publicly accessible URL for the deployed content, leveraging EdgeOne Pages Edge Functions and KV Store for fast edge delivery.

How to use EdgeOne Pages MCP?

To use EdgeOne Pages MCP, you need Node.js 18 or higher. You can configure it as a stdio MCP Server or a Streamable HTTP MCP Server. For stdio, you can optionally provide EDGEONE_PAGES_API_TOKEN and EDGEONE_PAGES_PROJECT_NAME environment variables. The service accepts HTML content through the deploy_html tool, connects to the EdgeOne Pages API to get the base URL, deploys the content using the EdgeOne Pages KV API, and returns a publicly accessible URL.

Key Features of EdgeOne Pages MCP

• MCP Protocol Integration: Enables rapid deployment of HTML content to EdgeOne Pages.
• Automatic URL Generation: Automatically generates publicly accessible URLs for deployed content.
• EdgeOne Pages Functions Integration: Utilizes EdgeOne Pages Functions for serverless execution at the edge.
• EdgeOne Pages KV Store: Stores and serves HTML content using the EdgeOne Pages KV store for fast access.
• Error Handling: Handles API errors with appropriate messages.

Use Cases of EdgeOne Pages MCP

• Rapid HTML Deployment: Quickly deploy static HTML content to the edge.
• Content Delivery: Serve web content with fast edge delivery for improved user experience.
• Integration with LLMs: Deploy HTML content generated by Large Language Models.
• Dynamic Content Updates: Update existing EdgeOne Pages projects by providing a project name.

FAQ about EdgeOne Pages MCP

• What are the requirements for running EdgeOne Pages MCP? Node.js 18 or higher is required.

• How do I obtain my EdgeOne Pages API token? Refer to the EdgeOne documentation for instructions on obtaining your API token.

• Can I update an existing EdgeOne Pages project? Yes, you can provide an existing project name in the EDGEONE_PAGES_PROJECT_NAME environment variable to update it.

• Where is the deployed content stored? The content is stored in the EdgeOne Pages KV Store for fast edge access.

• What kind of content can I deploy? You can deploy HTML content, folders, and zip files.

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