Self-Hosted EdgeOne Pages

Provides a self-hosted MCP server to deploy and manage static websites via an HTTP MCP endpoint and API access.

other

0

GitHub Stars

other

Language

4 months ago

First Indexed

2 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 can run a self-hosted EdgeOne Pages MCP Server to deploy and manage your static websites through an MCP client. It provides a centralized way to serve pages, store files, and expose a simple API for content updates.

How to use

Use an MCP client to connect to your EdgeOne Pages MCP Server and manage your static site content. You can deploy new content, bind a custom domain, and perform API-based updates. The primary endpoint is the MCP URL you configure for your server, which enables you to add and fetch page data, organize site files, and trigger updates from your tooling.

How to install

Prerequisites: you should have a hosting environment capable of serving HTTP endpoints and, optionally, a domain you own for binding a custom URL.

Step 1. Deploy the MCP server using the one-click option. You will receive a dedicated MCP URL after deployment.

Step 2. Add the MCP server configuration to your MCP client configuration so the client can reach your server.

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

Direct API Access

You can update content directly via the MCP API by sending a request to your server’s KV store endpoint.

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