home / mcp / self-hosted edgeone pages mcp server
Provides an MCP endpoint to deploy and manage static websites via EdgeOne Pages with KV storage and domain binding.
Configuration
View docs{
"mcpServers": {
"hply-self-hosted-pages-mcp": {
"url": "https://your-custom-domain.com/mcp-server"
}
}
}This MCP server lets you self-host EdgeOne Pages content management via the Model Context Protocol, enabling AI assistants to deploy and manage your static websites with a simple setup and ready-to-use flow.
Connect your MCP client to the EdgeOne Pages MCP endpoint to manage and deploy your static sites. Use the http-based MCP connection to reference the remote server, and leverage the API to publish pages, retrieve content, and manage storage through KV-backed operations. You can combine this with the KV storage and domain binding steps to publish a live site accessed via your dedicated URL.
Prerequisites: ensure you have a supported runtime environment and network access to the MCP server. You need a client capable of working with MCP endpoints and configuring the remote server URL.
Step 1. Deploy the MCP server using the one-click option.
Step 2. After deployment, configure the MCP client to connect to your MCP server using the provided endpoint.
{
"mcpServers": {
"edgeone-pages": {
"url": "https://your-custom-domain.com/mcp-server"
}
}
}Set up KV Storage to store website files and data. Bind a custom domain to obtain your dedicated access URL. These steps ensure your content is stored securely and served from a stable public address.
You can also deploy content directly via API. This example shows how to set a value in KV storage that can be retrieved by your MCP-enabled client.
curl -X POST https://your-custom-domain.com/kv/set \
-H "Content-Type: application/json" \
-d '{"value": "<html><body><h1>Hello, World!</h1></body></html>"}'One-click deployment of the MCP server to EdgeOne Pages.
Add MCP server configuration to your MCP setup.
Set up KV storage to store website files and data.
Bind a custom domain to obtain a dedicated access URL.
Deploy content directly via API using KV storage and MCP endpoints.