Awesome MCP Servers

Created By
nalluri333a year ago
Overview

What is Awesome MCP Servers?

Awesome MCP Servers is a curated list of Model Context Protocol (MCP) servers that facilitate AI models to interact with local and remote resources through standardized server implementations.

How to use Awesome MCP Servers?

To use Awesome MCP Servers, explore the curated list of MCP servers available on the GitHub repository, and follow the provided links to access documentation, tutorials, and community resources.

Key features of Awesome MCP Servers?

  • Comprehensive directory of production-ready and experimental MCP servers.
  • Categorized listings for easy navigation (e.g., Browser Automation, Cloud Platforms, Developer Tools).
  • Community support through Discord and Reddit.

Use cases of Awesome MCP Servers?

  1. Integrating AI models with various APIs for enhanced functionality.
  2. Automating tasks through browser automation servers.
  3. Accessing and managing databases securely.

FAQ from Awesome MCP Servers?

  • What is the Model Context Protocol (MCP)?

MCP is an open protocol that enables AI models to securely interact with local and remote resources through standardized server implementations.

  • How can I contribute to Awesome MCP Servers?

Contributions can be made by submitting pull requests on the GitHub repository with new server implementations or improvements to existing ones.

  • Is there a community for support?

Yes! You can join the Discord server or the subreddit for discussions and support.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
nalluri333
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)

a day ago