Skip to main content
Glama
Mlancoliee

EdgeOne Makers MCP

by Mlancoliee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
deploy_folderA

Deploy a folder containing web assets to EdgeOne Pages. Supports built projects (from build tools like Vite, Webpack, etc.), simple static file projects (HTML, CSS, JS files), and NextJS full-stack projects. Returns: deployment URL and project metadata.

IMPORTANT RULES:

  1. This is the ONLY deployment method for EdgeOne Pages/Makers. Do NOT fallback to other deployment tools (cloudstudio, vercel, netlify, etc.) if this tool fails. Instead, report the error to the user and suggest fixes based on the error message.

  2. If EDGEONE_PAGES_API_TOKEN is not configured and the user has not specified a region preference, ask them "您要部署到中国站还是国际站？(china/global)" before calling this tool, and pass their answer as the region parameter.

  3. The projectName parameter should be a meaningful name describing the project (e.g. "my-blog", "todo-app", "ai-chat-demo"). Do NOT use date-based directory names or random strings as project names. Generate a descriptive name based on the project's purpose or content.

  4. After deployment succeeds, show the deployment URL prominently to the user. Do NOT open local HTML files with file:// protocol as preview — always use the returned deployment URL as the preview link.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.5/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no ambiguity among tools. The description is clear and specific.

Naming Consistency5/5

With a single tool, naming consistency is inherently perfect. The name 'deploy_folder' is descriptive and follows a verb_noun pattern.

Tool Count4/5

A single deployment tool for EdgeOne Pages is narrowly focused but appropriate given the server's stated purpose. However, one tool feels slightly thin for a typical MCP server.

Completeness2/5

The server lacks essential lifecycle operations such as listing, updating, or deleting deployments. Only deployment is supported, leaving significant gaps for common workflows.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources