Awesome MCP Servers 🌟

Created By
sanjay200630a year ago
A comprehensive collection of Model Context Protocol (MCP) servers
Overview

What is Awesome MCP Servers?

Awesome MCP Servers is a comprehensive collection of Model Context Protocol (MCP) servers designed to help developers and enthusiasts explore and implement MCP solutions for managing context in distributed systems.

How to use Awesome MCP Servers?

To use Awesome MCP Servers, clone the repository from GitHub, check the releases for the latest server files, and follow the specific instructions in the documentation to run the server.

Key features of Awesome MCP Servers?

  • Diverse server implementations catering to different use cases.
  • Easy integration into existing systems.
  • Comprehensive documentation for quick setup and usage.
  • Community contributions are welcomed to enhance the repository.

Use cases of Awesome MCP Servers?

  1. Implementing context management in distributed applications.
  2. Facilitating seamless communication between various system components.
  3. Exploring different MCP server implementations for specific needs.

FAQ from Awesome MCP Servers?

  • How can I contribute to Awesome MCP Servers?

You can contribute by forking the repository, making changes, and submitting a pull request.

  • Is there documentation available for each server?

Yes! Comprehensive documentation is provided for each server to help you get started quickly.

  • What license is Awesome MCP Servers under?

This project is licensed under the MIT License.

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

2 days ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago