MCP_Servers

Created By
Baptoshia year ago
Top MCP Servers to use with AI
Overview

What is MCP_Servers?

MCP_Servers is a comprehensive analysis of the most interesting Model Context Protocol (MCP) servers, focusing on their utility in AI-driven workflows and discussions from the platform X.

How to use MCP_Servers?

Users can explore the analysis by visiting the GitHub repository, which provides insights into various MCP servers, their features, and setup links for integration with AI tools like Claude Desktop.

Key features of MCP_Servers?

  • Detailed analysis of top MCP servers based on user discussions and recommendations.
  • Categorization of servers by functionality such as cloud platforms, communication, and finance.
  • Links to setup guides and additional resources for each server.

Use cases of MCP_Servers?

  1. Automating content curation and engagement analysis with Reddit MCP Server.
  2. Managing knowledge and tasks using Notion MCP Server.
  3. Real-time data management with Google Sheets MCP Server.
  4. Email automation and scheduling through Gmail MCP Server.
  5. Community engagement and event coordination with Discord MCP Server.

FAQ from MCP_Servers?

  • What are MCP servers?

MCP servers are platforms that utilize the Model Context Protocol to connect AI models with various data sources securely.

  • How can I set up an MCP server?

Each server listed in the analysis includes a setup link for easy integration with AI tools.

  • Are there any notable MCP servers?

Yes, the analysis highlights several notable servers including Reddit, Notion, Google Sheets, Gmail, and Discord, each with unique features.

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