Model Context Protocol (MCP) Server

Created By
shaswata56a year ago
Overview

what is Model Context Protocol (MCP) Server?

The Model Context Protocol (MCP) Server is a modular server designed for AI services, allowing dynamic service selection and multiple transport options, built with SOLID principles for maintainability and extensibility.

how to use MCP Server?

To use the MCP Server, clone the repository, set up a virtual environment, install dependencies, and configure your environment variables in the .env file. You can run the server in different modes: standard, TCP, or WebSocket.

key features of MCP Server?

  • Supports multiple AI services including Claude and OpenAI.
  • Dynamic service selection on a per-request basis.
  • Multiple transport options: stdio, TCP, and WebSocket.
  • JSON-RPC 2.0 compliant interface for predictable interactions.
  • Modular architecture for easy extension with new services and transports.
  • Real-time response streaming for supported transports.

use cases of MCP Server?

  1. Integrating various AI services into applications.
  2. Real-time data processing and interaction through WebSocket.
  3. Command-line tools for AI service interaction.

FAQ from MCP Server?

  • What AI services does MCP Server support?

MCP Server supports Claude, OpenAI, and mock services for testing.

  • How can I run the server?

You can run the server in standard, TCP, or WebSocket mode using command line options.

  • Is there a way to extend the server?

Yes! You can add new method handlers, AI services, or transports by following the provided guidelines in the documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
shaswata56
Star
0
Language
Python
License
MIT 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)

a day ago