Temp

Created By
TencentEdgeOne8 months ago
Overview

what is EdgeOne Pages MCP?

EdgeOne Pages MCP is a service designed for deploying HTML content, folders, or full-stack projects to EdgeOne Pages, providing users with publicly accessible URLs for their deployed content.

how to use EdgeOne Pages MCP?

To use EdgeOne Pages MCP, you need to install Node.js 18 or higher and run the command npx edgeone-pages-mcp with the appropriate parameters to deploy your HTML or folder content.

key features of EdgeOne Pages MCP?

  • Deploys static HTML content and full-stack applications.
  • Automatically generates publicly accessible URLs for each deployment.
  • Supports both deploy_html and deploy_folder tools for flexible deployment options.

use cases of EdgeOne Pages MCP?

  1. Deploying static websites quickly and efficiently.
  2. Hosting full-stack applications with ease.
  3. Updating existing projects or creating new ones seamlessly.

FAQ from EdgeOne Pages MCP?

  • What is required to use EdgeOne Pages MCP?

You need Node.js 18 or higher installed on your machine.

  • Can I deploy full-stack applications?

Yes! EdgeOne Pages MCP supports the deployment of full-stack applications.

  • Is the source code available?

Yes! The source code is open source and can be found on GitHub.

Server Config

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

Recommend Servers

View All
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)

20 hours ago
Gpt Scrambler

2 days ago