MCP-Server 项目文档

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is MCP-Server?

MCP-Server is a server and client implementation based on the Model Context Protocol (MCP), allowing large language models (LLMs) to call external tools through a structured protocol to complete complex tasks.

How to use MCP-Server?

To use MCP-Server, start the server and client, then access the Web API to send queries. For example, to check the weather in Beijing, send a POST request to the /sse endpoint with the appropriate query.

Key features of MCP-Server?

  • Tool registration for various services like weather and GitHub user information.
  • Execution of tools based on client requests.
  • Communication through standard input/output with the client.
  • White-box process visualization to understand the model's decision-making.

Use cases of MCP-Server?

  1. Querying real-time weather information.
  2. Retrieving user data from GitHub.
  3. Enhancing LLM capabilities by integrating external APIs.

FAQ from MCP-Server?

  • What programming languages are used in MCP-Server?

The backend is built with Node.js and TypeScript.

  • How do I set up the environment?

You need to configure the .env file with the required API keys for LLM and other services.

  • Can I extend MCP-Server with additional tools?

Yes! You can register new tools in the MCP server to extend its functionality.

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