Edgeone

Created By
TencentEdgeOnea year ago
Overview

what is EdgeOne Pages MCP?

EdgeOne Pages MCP is a service designed for deploying HTML content, folders, and zip files to EdgeOne Pages, providing users with publicly accessible URLs for their content.

how to use EdgeOne Pages MCP?

To use EdgeOne Pages MCP, you can deploy HTML content or folders/zip files by using the provided commands in the MCP server. After deployment, the service will return a public URL for accessing the content.

key features of EdgeOne Pages MCP?

  • Rapid deployment of HTML content to EdgeOne Pages.
  • Automatic generation of publicly accessible URLs for deployed content.
  • Integration with EdgeOne Pages Functions for serverless computing.

use cases of EdgeOne Pages MCP?

  1. Deploying static websites quickly and efficiently.
  2. Sharing HTML content with a public URL for easy access.
  3. Hosting web applications using serverless architecture.

FAQ from EdgeOne Pages MCP?

  • What is required to use EdgeOne Pages MCP?

You need Node.js version 18 or higher to run the MCP service.

  • How do I obtain my EdgeOne Pages API token?

You can find instructions on how to obtain your API token in the EdgeOne documentation.

  • Can I deploy folders or zip files?

Yes, EdgeOne Pages MCP supports deploying both folders and zip files.

Server Config

{
  "mcpServers": {
    "edgeone-pages-mcp-server": {
      "command": "npx",
      "args": [
        "edgeone-pages-mcp"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
10 months ago
Author Name
TencentEdgeOne
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

37 minutes ago