EdgeOne Pages MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EDGEONE_PAGES_API_TOKEN | No | Your EdgeOne Pages API token. Optional. If you need to deploy folders or zip files to EdgeOne Pages projects, provide your EdgeOne Pages API token. | |
| EDGEONE_PAGES_PROJECT_NAME | No | EdgeOne Pages project name. Optional. Leave empty to create a new EdgeOne Pages project. Provide a project name to update an existing project. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| deploy_htmlC | Deploy HTML content to EdgeOne Pages, return the public URL |
| deploy_folder_or_zipC | Deploy a built frontend directory (or zip file) to EdgeOne Pages. Returns: the deployment URL and project metadata. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one deploys a folder or zip file for a built frontend, while the other deploys raw HTML content. There is no overlap or ambiguity between them, making it easy for an agent to select the correct tool based on the input type.
Both tools follow a consistent verb_noun pattern with 'deploy' as the verb, and the nouns ('folder_or_zip', 'html') clearly indicate the target. The naming is uniform and predictable across the set.
With only 2 tools, the server feels thin for a deployment service. While the tools cover basic deployment scenarios, typical MCP servers for such domains (like GitHub or cloud services) offer more operations (e.g., list deployments, update, delete, monitor status), suggesting this set is under-scoped and may leave gaps in agent workflows.
The server lacks essential operations for a deployment domain, such as listing existing deployments, updating or deleting them, checking status, or managing projects. This creates significant gaps that could cause agent failures when trying to perform full lifecycle management, as agents cannot retrieve or modify past deployments.