Top MCP Servers

What is Top MCP Servers?

A curated collection of top Model Context Protocol (MCP) servers for enhancing development workflows in 2025, including web automation, GitHub integration, and persistent memory management.

How to use Top MCP Servers?

Clone the repository, install npm dependencies, configure a GitHub personal access token in a .env file, then use the MCP configurations in .cursor/mcp.json. Each MCP (Playwright, GitHub, Memory) can be used independently or together.

Key features of Top MCP Servers

• Web automation with Playwright and Puppeteer MCPs
• GitHub repository, issue, PR, and code search management
• Persistent knowledge storage and knowledge graph management
• Cross-session context retention via Memory MCP
• Headless browser automation and web scraping support

Use cases of Top MCP Servers

• Automate weather checks and page screenshots with Playwright or Puppeteer
• Manage GitHub repositories, issues, and pull requests programmatically
• Store and retrieve project knowledge across sessions using Memory MCP
• Scrape dynamic web pages for data extraction and monitoring

FAQ from Top MCP Servers

What runtime does Top MCP Servers require?

Node.js and npm are required; install dependencies with npm install.

How do I configure GitHub access?

Create a .env file and set GITHUB_PERSONAL_ACCESS_TOKEN=your_token_here.

Where is data stored when using the Memory MCP?

The Memory MCP stores knowledge persistently on the local filesystem.

What authentication does the GitHub MCP use?

It uses a personal access token provided via the .env file.

Are there any known limits or deployment notes?

The project is deployed on render.com; headless browser MCPs may require system dependencies for sandboxed browser execution.