home / mcp / edgeone pages mcp server

EdgeOne Pages MCP Server

An MCP service designed for deploying HTML content to EdgeOne Pages and obtaining an accessible public URL.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "tencentedgeone-edgeone-pages-mcp": {
      "url": "https://mcp-on-edge.edgeone.site/mcp-server",
      "headers": {
        "EDGEONE_PAGES_API_TOKEN": "<EDGEONE_PAGES_API_TOKEN>",
        "EDGEONE_PAGES_PROJECT_NAME": "<EDGEONE_PAGES_PROJECT_NAME>"
      }
    }
  }
}

You deploy and publish HTML content, folders, or full-stack projects to EdgeOne Pages with an MCP server, then obtain publicly accessible URLs for fast edge delivery. This guide helps you use the MCP server to deploy content and manage deployments efficiently.

How to use

You interact with the MCP server through an MCP client. Choose a config that matches how you want to deploy: a remote HTTP MCP server for centralized, always-on access, or a local stdio MCP server that you run on demand with your own tooling. The server handles deployment to EdgeOne Pages Functions, stores content in EdgeOne KV, and returns a public URL you can share. When you deploy, you get a URL that serves your content quickly from the edge.

Key deployment options include deploying static HTML content and deploying full projects or full-stack apps. If you need a serverless or edge-enabled deployment path, you can opt for the stdio flow that you run locally via MCP tooling, or use the HTTP flow to connect to an MCP endpoint directly.

How to install

Prerequisites you need before starting are Node.js 18 or higher.

Verify your Node.js and npm installation, then start the MCP client that runs the deployment tooling.

node -v
npm -v
npx edgeone-pages-mcp-fullstack@latest
npx edgeone-pages-mcp-fullstack@latest --region china

Configuration and important notes

You can deploy content using multiple MCP server configurations. The following configurations are explicitly provided for EdgeOne Pages deployments.

HTTP deployment (remote MCP URL) provides a public, centralized endpoint you can point your MCP client at.

STDIO deployment (local MCP server) runs via npx and deploys content directly to EdgeOne Pages from your workflow.

Tool details

deploy_html Tool – deploys static HTML content to EdgeOne Pages, stores content in the edge KV store, and returns a public URL for immediate access. It integrates with EdgeOne Pages Functions to execute at the edge and provides robust error handling.

deploy_folder Tool – deploys complete static projects or full-stack applications to EdgeOne Pages, with options to update existing projects or create new ones.

Examples of MCP server configurations

{
  "mcpServers": {
    "edgeone_pages_mcp": {
      "timeout": 600,
      "command": "npx",
      "args": ["edgeone-pages-mcp-fullstack@latest"]
    }
  }
}

Additional HTTP and legacy configurations

{
  "mcpServers": {
    "edgeone_pages_mcp_cn": {
      "timeout": 600,
      "command": "npx",
      "args": ["edgeone-pages-mcp-fullstack@latest", "--region", "china"]
    }
  }
}

Legacy single-tool MCP (deprecated)

{
  "mcpServers": {
    "edgeone_mcp_old": {
      "command": "npx",
      "args": ["edgeone-pages-mcp@latest"],
      "env": {
        "EDGEONE_PAGES_API_TOKEN": "",
        "EDGEONE_PAGES_PROJECT_NAME": ""
      }
    }
  }
}

Streaming HTTP MCP Server

{
  "mcpServers": {
    "edgeone_http_mcp": {
      "url": "https://mcp-on-edge.edgeone.site/mcp-server",
      "type": "http",
      "args": []
    }
  }
}

Available tools

deploy_html

Deploys HTML content to EdgeOne Pages, stores on KV, and returns a public URL with edge-fast delivery.

deploy_folder

Deploys a complete folder or full-stack project to EdgeOne Pages with options to update or create a new project.