- Explore MCP Servers
- edgeone-pages-mcp
EdgeOne Pages MCP
What is EdgeOne Pages MCP
EdgeOne Pages MCP is a service designed for deploying HTML content, folders, and zip files to EdgeOne Pages. It enables users to obtain a publicly accessible URL for the deployed content, effectively allowing for fast edge delivery of websites and applications.
Use cases
Common use cases include quickly deploying static HTML web pages, updating existing projects with new content, and managing collections of files under an EdgeOne Pages project. This service is particularly useful for developers looking to leverage serverless edge computing for better performance.
How to use
To use EdgeOne Pages MCP, you need to configure it either as a standard MCP server by providing a Node.js environment with necessary API tokens or as a streamable HTTP server. Users can deploy HTML content directly with a command or by using the EdgeOne Pages API to manage and update existing projects.
Key features
Key features include rapid deployment of HTML content, automatic generation of publicly accessible URLs, integration with the EdgeOne Pages KV store for storing content, and robust error handling to provide clear feedback on API interactions.
Where to use
EdgeOne Pages MCP is suitable for applications that require high-performance web delivery, especially those hosted on EdgeOne infrastructure. It is ideal for static sites, web applications, and any projects that benefit from serverless architecture in edge computing environments.
Overview
What is EdgeOne Pages MCP
EdgeOne Pages MCP is a service designed for deploying HTML content, folders, and zip files to EdgeOne Pages. It enables users to obtain a publicly accessible URL for the deployed content, effectively allowing for fast edge delivery of websites and applications.
Use cases
Common use cases include quickly deploying static HTML web pages, updating existing projects with new content, and managing collections of files under an EdgeOne Pages project. This service is particularly useful for developers looking to leverage serverless edge computing for better performance.
How to use
To use EdgeOne Pages MCP, you need to configure it either as a standard MCP server by providing a Node.js environment with necessary API tokens or as a streamable HTTP server. Users can deploy HTML content directly with a command or by using the EdgeOne Pages API to manage and update existing projects.
Key features
Key features include rapid deployment of HTML content, automatic generation of publicly accessible URLs, integration with the EdgeOne Pages KV store for storing content, and robust error handling to provide clear feedback on API interactions.
Where to use
EdgeOne Pages MCP is suitable for applications that require high-performance web delivery, especially those hosted on EdgeOne infrastructure. It is ideal for static sites, web applications, and any projects that benefit from serverless architecture in edge computing environments.
Content
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
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:
- Large Language Model generates HTML content
- Content is sent to the EdgeOne Pages MCP Server
- MCP Server deploys the content to EdgeOne Pages Edge Functions
- Content is stored in EdgeOne KV Store for fast edge access
- MCP Server returns a public URL
- 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:
-
EdgeOne Pages Functions - A serverless computing platform that allows execution of JavaScript/TypeScript code at the edge.
-
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
-
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
- The MCP server accepts HTML content through the
-
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