- Home
- MCP servers
- Cang Pages
Cang Pages
- other
0
GitHub Stars
other
Language
5 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.
This self-hosted MCP server lets you deploy and manage static websites through an MCP-enabled control plane. It provides a simple path to host content, store files, and bind a custom domain for direct access, all from your own infrastructure.
How to use
You interact with the MCP server through an MCP client or API to manage your static sites. Start by pointing the client to your server’s MCP endpoint, then publish or update your site content, and bind a custom domain for public access. The server coordinates storage, content delivery, and basic site management tasks, so you can focus on building pages rather than plumbing.
How to install
Prerequisites: ensure you have a running environment capable of hosting an MCP server. You will typically need access to a domain, a storage mechanism for your files (KV storage), and the ability to expose an HTTPS URL for your MCP endpoint.
Step 1. Deploy the MCP server using the one-click method. Follow the prompt to create your instance and choose EdgeOne Pages as the hosting provider.
Step 2. Add the MCP server configuration to your MCP client config. Include the URL for your deployed MCP server as shown below.
{
"mcpServers": {
"edgeone-pages": {
"url": "https://your-custom-domain.com/mcp-server"
}
}
}
Direct API Access
You can publish content directly via API by sending a KV set request to your server. This enables quick, programmatic updates to site content without a UI.
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>"}'
Available tools
kv_storage
KV storage integration used to store and retrieve website files and metadata for MCP-backed websites.
domain_binding
Mechanism to bind and manage a custom domain for your MCP-hosted site, enabling direct public access.
content_publish
API-driven content publishing to deploy or update static site pages through the MCP server.