Self-Hosted EdgeOne Pages

Provides an MCP-enabled endpoint to deploy and manage static websites via HTTP, with optional KV storage API access.

other

0

GitHub Stars

other

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

You deploy and manage a self-hosted MCP server that enables AI assistants to deploy and manage static websites through a simple, ready-to-use setup. It provides a dedicated HTTP endpoint to connect your MCP client and optional direct API access for content operations.

How to use

Connect your MCP client to the HTTP MCP endpoint for EdgeOne Pages. Use the provided server URL to register the MCP connection in your client configuration. Once connected, you can deploy, update, and serve static website content through the MCP server, enabling AI assistants to fetch and display pages directly. You can also publish content via the direct API shown in the example to store HTML assets on the MCP-backed KV storage.

How to install

Follow these practical steps to get your EdgeOne Pages MCP server up and running.

Start with the one-click deploy URL to provision your MCP server environment.
After deployment, add the MCP server configuration to your MCP client or server config file using the endpoint provided here:

{
  "mcpServers": {
    "edgeone-pages": {
      "url": "https://your-custom-domain.com/mcp-server"
    }
  }
}

Direct API Access

You can publish content directly via API calls to your MCP-backed KV storage. Use the following example to store HTML content that your MCP clients can retrieve.

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>"}'