MCP Server

Created By
hewenyua year ago
一部分mcp 服务自动打包
Overview

what is MCP Server?

MCP Server is a project that provides a deployment environment for the context7 service using Docker and Nginx, allowing for easy setup and management of the service.

how to use MCP Server?

To use MCP Server, clone the repository, navigate to the deployment directory, and start the services using Docker Compose. Access the service via your web browser.

key features of MCP Server?

  • Dockerized Deployment: Easily deploy the context7 service using Docker Compose.
  • Nginx Reverse Proxy: Proxies all HTTP requests to the context7 service, supporting SSE streaming.
  • CI/CD Support: Includes GitHub Actions workflow for building and pushing Docker images.

use cases of MCP Server?

  1. Deploying the context7 service in a containerized environment.
  2. Managing HTTP requests through Nginx for better performance.
  3. Automating Docker image builds and deployments with CI/CD.

FAQ from MCP Server?

  • Can MCP Server be used for other services?

While designed for context7, MCP Server can be adapted for other services with similar requirements.

  • Is there a license for MCP Server?

Yes, MCP Server is licensed under the GNU General Public License v3.0.

  • How do I access the deployed service?

After starting the services, you can access the service by visiting http://localhost in your web browser.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
hewenyu
Star
0
Language
-
License
GPL-3.0 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