EdgeOne Pages: MCP Client and Server Implementation with Functions

Created By
xixiana year ago
MCP Client and Server Implementation with Functions
Overview

what is MCP on Edge?

MCP on Edge is an intelligent chat application that implements the Model Context Protocol (MCP) using EdgeOne Pages Functions technology, allowing users to interact with backend functions through a web interface.

how to use MCP on Edge?

To use MCP on Edge, set up the environment by installing dependencies, configure the necessary environment variables, and start the development server. Access the application via your browser at http://localhost:3000.

key features of MCP on Edge?

  • Interactive chat interface built with Next.js and React
  • High-performance Edge Functions for scalable business logic
  • Complete implementation of the Model Context Protocol for context management
  • OpenAI format compatibility for request and response handling

use cases of MCP on Edge?

  1. Building intelligent chatbots that can generate responses based on context.
  2. Creating web applications that require real-time data processing and interaction.
  3. Implementing backend services that utilize the Model Context Protocol for efficient communication.

FAQ from MCP on Edge?

  • What is the Model Context Protocol (MCP)?

MCP is a protocol designed for managing context in interactions, allowing for more intelligent and context-aware applications.

  • Is MCP on Edge free to use?

Yes! MCP on Edge is free to use for development purposes.

  • What technologies are used in MCP on Edge?

The project uses Next.js, React, and EdgeOne Pages Functions for its implementation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
xixian
Star
0
Language
TypeScript
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)

2 days ago