Model Context Protocol servers

Created By
thanhvinh199700a year ago
Overview

What is MCP-SERVER?

MCP-SERVER is a repository containing reference implementations for the Model Context Protocol (MCP), showcasing how it can be utilized to provide Large Language Models (LLMs) with secure and controlled access to various tools and data sources.

How to use MCP-SERVER?

To use MCP-SERVER, you can run the servers directly using npx for TypeScript-based servers or uvx/pip for Python-based servers. Configuration examples for integrating with clients like Claude Desktop are also provided in the documentation.

Key features of MCP-SERVER?

  • A collection of reference implementations for MCP.
  • Support for both TypeScript and Python SDKs.
  • Demonstrates various integrations with third-party services like AWS, Google Drive, and more.
  • Community-driven with a growing set of servers for diverse applications.

Use cases of MCP-SERVER?

  1. Enabling LLMs to interact with cloud services like AWS and Google Drive.
  2. Facilitating secure file operations and database interactions.
  3. Providing a framework for building custom MCP servers.

FAQ from MCP-SERVER?

  • What is the Model Context Protocol?

The Model Context Protocol is a framework that allows LLMs to access tools and data securely and efficiently.

  • Is MCP-SERVER free to use?

Yes! MCP-SERVER is open-source and free to use under the MIT License.

  • How can I contribute to MCP-SERVER?

Contributions are welcome! Please refer to the contributing guidelines in the repository.

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