Edgeone Pages Mcp Server

Created By
TencentEdgeOnea year ago
Overview

what is EdgeOne Pages MCP?

EdgeOne Pages MCP is a service designed for deploying HTML content to EdgeOne Pages, allowing users to obtain publicly accessible URLs for their content.

how to use EdgeOne Pages MCP?

To use EdgeOne Pages MCP, you need to provide HTML content to the MCP service, which will then deploy it and return a public URL for access.

key features of EdgeOne Pages MCP?

  • Rapid deployment of HTML content using the MCP protocol.
  • Automatic generation of publicly accessible URLs for deployed content.

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. Integrating with EdgeOne Pages Functions for serverless applications.

FAQ from EdgeOne Pages MCP?

  • What is the MCP protocol?

The MCP protocol is a method for deploying content rapidly to EdgeOne Pages.

  • How do I get a public URL for my content?

The service automatically generates a public URL upon successful deployment of your HTML content.

  • Is there any cost associated with using EdgeOne Pages MCP?

Please refer to the EdgeOne pricing documentation for details on any potential costs.

Server Config

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

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago