EdgeOne Pages MCP
MCP ServerFree** - An MCP service for deploying HTML content to EdgeOne Pages and obtaining a publicly accessible URL.
Capabilities8 decomposed
mcp-compliant html deployment to edge cdn with public url generation
Medium confidenceDeploys static HTML content to Tencent EdgeOne Pages via the Model Context Protocol (MCP) standard, leveraging a KV store backend for content persistence and returning immediately accessible public URLs. The system implements both stdio and HTTP transport mechanisms, allowing seamless integration with MCP-enabled LLM applications and agents that need to publish generated content to a globally distributed edge network without managing infrastructure.
Implements MCP as a first-class protocol for content deployment rather than wrapping a REST API, enabling native integration with LLM applications through standardized tool calling. Uses installation ID-based state management to track deployments within EdgeOne's KV store, avoiding external persistence requirements while maintaining deployment history.
Tighter MCP integration than generic deployment tools, allowing LLMs to deploy content as a native capability without custom API wrappers or authentication handling.
stdio and http transport abstraction for mcp server communication
Medium confidenceProvides dual transport layer implementations (stdio for CLI/local integration and HTTP for web-based clients) that abstract the underlying communication protocol while maintaining MCP specification compliance. The transport layer handles message serialization, protocol negotiation, and bidirectional streaming, allowing the same deployment logic to serve both command-line tools and web applications without code duplication.
Implements transport abstraction at the MCP server level using a pluggable architecture (stdio vs HTTP), allowing configuration-driven selection without code changes. Maintains protocol-level compatibility while supporting fundamentally different communication patterns (process-based vs network-based).
More flexible than single-transport MCP implementations, enabling deployment in diverse environments (CLI, web servers, cloud functions) from a single codebase.
installation id-based deployment state management and tracking
Medium confidenceManages deployment lifecycle through unique installation IDs that serve as identifiers for each HTML deployment to EdgeOne Pages. The system generates or retrieves installation IDs, associates them with deployed content in the KV store, and uses them to construct public URLs. This approach provides lightweight state tracking without requiring external databases, leveraging EdgeOne's infrastructure for both storage and URL generation.
Uses EdgeOne's native KV store as the state backend rather than introducing external persistence, embedding deployment state directly in the content delivery infrastructure. Installation IDs serve dual purpose: unique identifiers for tracking and URL components for public access.
Eliminates external database dependencies compared to traditional deployment systems, reducing operational complexity while leveraging the CDN's native storage for state.
edgeone pages api integration with kv store content persistence
Medium confidenceIntegrates with Tencent EdgeOne Pages API to request base URLs and deploy HTML content to the platform's KV store backend. The integration handles API authentication, content upload to the distributed KV store, and URL construction, abstracting EdgeOne's deployment complexity behind a simple tool interface. The KV store provides global edge caching and persistence without requiring manual infrastructure management.
Abstracts EdgeOne Pages API as a deployment backend through MCP, handling authentication and KV store operations transparently. Leverages EdgeOne's native KV store for content persistence, avoiding separate storage infrastructure while maintaining edge caching benefits.
Simpler than managing EdgeOne API directly from LLM applications, providing a standardized MCP interface that handles authentication, error handling, and URL construction automatically.
mcp tool schema definition and parameter validation for deploy-html
Medium confidenceDefines the deploy-html tool as an MCP-compliant tool with JSON schema validation, parameter documentation, and type safety. The tool schema specifies input parameters (HTML content), output format (public URL), and error handling, enabling LLM applications to understand and invoke the deployment capability with proper type checking. Schema-based invocation ensures that LLMs provide correctly formatted HTML and receive structured responses.
Implements deploy-html as a formally specified MCP tool with JSON schema validation, enabling LLMs to understand and safely invoke deployment without custom parsing or error handling. Schema-driven approach ensures type safety at the protocol level.
More robust than string-based tool descriptions, providing machine-readable specifications that enable LLMs to validate parameters before invocation and handle errors systematically.
sequence-based deployment workflow orchestration
Medium confidenceOrchestrates the multi-step deployment workflow: client submits HTML → MCP server requests base URL from EdgeOne API → server deploys content to KV store with installation ID → server returns public URL to client. The workflow is implemented as a coordinated sequence of API calls and state transitions, with error handling at each step. This orchestration abstracts the complexity of EdgeOne's deployment process into a single tool invocation.
Implements deployment as a coordinated sequence of EdgeOne API calls within a single MCP tool invocation, hiding multi-step complexity from the client. Workflow orchestration is embedded in the MCP server rather than delegated to the client, ensuring consistent behavior across all deployment requests.
Simpler than client-side workflow management, providing atomic deployment operations that either fully succeed or fail with clear error context, reducing client-side error handling complexity.
configuration-driven transport and server initialization
Medium confidenceProvides configuration options to select between stdio and HTTP transport mechanisms at server startup, allowing deployment environment flexibility without code changes. Configuration is read from environment variables or configuration files, enabling different deployment modes (CLI, containerized, serverless) through simple configuration changes. The initialization process sets up the selected transport, configures MCP protocol handlers, and registers the deploy-html tool.
Decouples transport mechanism selection from code through configuration-driven initialization, enabling the same codebase to operate in CLI, HTTP, and containerized environments. Configuration is applied at startup time, allowing environment-specific behavior without conditional logic.
More flexible than hardcoded transport selection, supporting diverse deployment scenarios through simple configuration changes rather than code branching or multiple builds.
public url generation and construction from deployment metadata
Medium confidenceConstructs publicly accessible HTTPS URLs from deployment metadata (installation ID, EdgeOne domain) after successful content deployment. The URL generation combines the EdgeOne Pages base domain with the installation ID to create a stable, globally accessible endpoint. URLs are immediately returned to the client and can be shared without additional configuration or DNS setup.
Generates URLs directly from installation IDs without additional API calls or DNS configuration, providing immediate public access to deployed content. URL construction is deterministic — same installation ID always produces the same URL.
Faster than traditional URL provisioning systems that require DNS setup or additional API calls, enabling instant sharing of deployed content.
Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.
Related Artifactssharing capabilities
Artifacts that share capabilities with EdgeOne Pages MCP, ranked by overlap. Discovered automatically through the match graph.
Cloudflare MCP Server
Manage Cloudflare Workers, KV, R2, and DNS via MCP.
decocms
Deco CMS — Self-hostable MCP Gateway for managing AI connections and tools
playwright-mcp
Playwright MCP server
Browser MCP
** (by UI-TARS) - A fast, lightweight MCP server that empowers LLMs with browser automation via Puppeteer’s structured accessibility data, featuring optional vision mode for complex visual understanding and flexible, cross-platform configuration.
mcp.natoma.ai
** – A Hosted MCP Platform to discover, install, manage and deploy MCP servers by **[Natoma Labs](https://www.natoma.ai)**
mcp-framework
Framework for building Model Context Protocol (MCP) servers in Typescript
Best For
- ✓AI agents and LLM applications that generate HTML and need instant publishing
- ✓Teams building MCP-enabled tools that require content delivery infrastructure
- ✓Developers integrating Tencent EdgeOne services into AI workflows
- ✓Developers building CLI tools that need MCP server capabilities
- ✓Teams deploying MCP services in containerized or serverless environments
- ✓Applications requiring both local and remote MCP server access patterns
- ✓Stateless deployment scenarios where external persistence is unavailable
- ✓Applications requiring lightweight deployment tracking without database overhead
Known Limitations
- ⚠Supports only static HTML content — no server-side rendering or dynamic backends
- ⚠Deployment latency depends on EdgeOne API response times and KV store write operations
- ⚠Installation ID management requires state tracking; no built-in persistence layer for deployment history
- ⚠Limited to EdgeOne Pages platform — not portable to other CDNs without architectural changes
- ⚠Stdio transport requires process-level communication — not suitable for distributed systems without process management
- ⚠HTTP transport adds network latency and requires proper TLS/authentication configuration in production
Requirements
Input / Output
UnfragileRank
UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.
About
** - An MCP service for deploying HTML content to EdgeOne Pages and obtaining a publicly accessible URL.
Categories
Alternatives to EdgeOne Pages MCP
Are you the builder of EdgeOne Pages MCP?
Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.
Get the weekly brief
New tools, rising stars, and what's actually worth your time. No spam.
Data Sources
Looking for something else?
Search →