Top MCP Servers

Created By
djpapzina year ago
A curated collection of top Model Context Protocol (MCP) servers for enhancing development workflows in 2025
Overview

What is Top MCP Servers?

Top MCP Servers is a curated collection of top Model Context Protocol (MCP) servers designed to enhance development workflows in 2025, showcasing various MCP implementations for web automation, GitHub integration, and persistent memory management.

How to use Top MCP Servers?

To use Top MCP Servers, clone the repository from GitHub, install the necessary dependencies, and configure your environment variables. Each MCP can be utilized independently or in combination with others.

Key features of Top MCP Servers?

  • Web Automation MCPs: Includes Playwright for headless browser automation and Puppeteer for web interaction and screenshots.
  • GitHub Integration MCP: Facilitates repository management, issue and PR handling, and file operations.
  • Memory MCP: Offers persistent knowledge storage, knowledge graph management, and cross-session context retention.

Use cases of Top MCP Servers?

  1. Automating web tasks like checking weather or taking screenshots.
  2. Managing GitHub repositories and issues programmatically.
  3. Storing and retrieving project-related knowledge across sessions.

FAQ from Top MCP Servers?

  • Can I use multiple MCPs together?

Yes! You can combine different MCPs to enhance your development workflow.

  • Is there a specific setup required?

You need to configure your GitHub token in the environment variables for the GitHub MCP to function properly.

  • How can I contribute to this project?

Contributions are welcome! You can submit a Pull Request on GitHub.

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