MCP (Model Context Protocol) Server

Created By
kritsanan1a year ago
Overview

what is MCP Server?

MCP Server is a simple implementation of the Model Context Protocol that supports real-time communication through WebSocket and REST API.

how to use MCP Server?

To use MCP Server, clone the repository, install the dependencies, and run the server using Node.js. You can then interact with the server via the provided API endpoints or WebSocket connections.

key features of MCP Server?

  • WebSocket server for real-time communication
  • REST API endpoints for easy interaction
  • Static file serving capabilities
  • CORS support for cross-origin requests

use cases of MCP Server?

  1. Building real-time applications that require instant data updates.
  2. Creating interactive web applications that utilize WebSocket for communication.
  3. Developing APIs that need to serve static files and handle CORS requests.

FAQ from MCP Server?

  • What are the prerequisites to run MCP Server?

You need Node.js (v14 or later) and npm to install the dependencies.

  • How do I run the server?

After installation, you can start the server with the command node server.js.

  • What ports does the server use?

By default, the server runs on port 3000, but you can change it by setting the PORT environment variable.

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