MCP Server Demo

Created By
pedro2sa year ago
Overview

What is MCP Server Demo?

MCP Server Demo is a demonstration project for a Multi-Channel Protocol (MCP) server. It serves as an example for implementing and testing functionalities related to the MCP protocol.

How to use MCP Server Demo?

To use MCP Server Demo, clone the repository, install the dependencies, and run the server. Connect to the server using a compatible MCP client.

Key features of MCP Server Demo?

  • Basic implementation of the MCP server.
  • Support for multiple communication channels.
  • Modular structure for easy extension.

Use cases of MCP Server Demo?

  1. Testing MCP protocol functionalities.
  2. Developing applications that require multi-channel communication.
  3. Learning about server implementation using Python.

FAQ from MCP Server Demo?

  • What are the requirements to run MCP Server Demo?

Python 3.12 or higher and dependencies listed in the pyproject.toml file.

  • Is there a specific client to connect to the server?

Any compatible MCP client can be used to connect to the server.

  • Can I extend the functionalities of the server?

Yes! The project has a modular structure that allows for easy extension.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
pedro2s
Star
0
Language
Python
License
-

Recommend Servers

View All
Voyei

2 hours 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