MyMCPTools
Lists6 min read

Top 10 Most Popular MCP Servers in 2026 (By Use & GitHub Stars)

The most widely-used MCP servers in 2026, ranked by popularity, GitHub stars, and real-world adoption. These are the servers developers install first.

By MyMCPTools Team·

With over 500 MCP servers in the ecosystem, which ones are developers actually using? We analyzed GitHub stars, installation patterns, and community discussion to identify the ten most popular MCP servers heading into mid-2026.

1. Filesystem MCP Server — 15,000+ GitHub Stars

The filesystem server is the most universally installed MCP server. It's the first one most developers add, and it remains essential across virtually every workflow — from coding to writing to research.

Why it's #1: File access is the foundation of every AI-assisted coding workflow. No server does more to justify the MCP setup investment immediately.

  • Read/write files with proper encoding
  • Directory navigation and search
  • Configurable access boundaries
  • Maintained by Anthropic (official)

2. GitHub MCP Server — 12,000+ Stars

GitHub's MCP server rapidly became one of the most starred in the ecosystem after GitHub released the official version in early 2025. For developers, it's the second installation after filesystem.

Why it's #2: Most software development work involves GitHub in some way. PRs, issues, code search, and repo browsing are daily activities that MCP unlocks for AI.

  • Issue and PR management
  • Code search across repositories
  • Commit history and diffs
  • Official GitHub-maintained server

3. PostgreSQL MCP Server — 8,500+ Stars

The PostgreSQL MCP server is the most popular database integration by far. Its schema introspection capability — letting AI understand your actual data model — is transformative for backend development.

Why it's #3: PostgreSQL is the dominant production database for web applications. Giving AI accurate schema context for query writing is enormously practical.

4. Brave Search MCP Server — 7,200+ Stars

Web search is one of the most frequent things people want AI to do. The Brave Search server delivers current, unfiltered search results without the rate limiting and terms-of-service concerns of scraping Google.

Why it's #4: Information that post-dates the training cutoff — docs, changelogs, error messages — requires real web search. Brave Search delivers this reliably.

5. Puppeteer MCP Server — 6,800+ Stars

Browser automation is a power-user capability that Puppeteer MCP makes accessible. From automated testing to web scraping to UI debugging, it covers a wide range of workflows.

Why it's #5: Browser control is a uniquely powerful capability that few other tools provide. The ability to "show me what the page looks like" is genuinely novel.

6. Playwright MCP Server — 6,300+ Stars

Playwright's MCP server is close behind Puppeteer in popularity, and preferred by many testing-focused developers for its more modern API and multi-browser support.

Why it's #6: Playwright is the current standard for end-to-end browser testing. Its MCP server lets AI write, run, and debug Playwright tests directly.

7. Slack MCP Server — 5,900+ Stars

For team-based developers, Slack holds vast amounts of context that never makes it into code comments or documentation. The Slack MCP server mines that institutional knowledge.

Why it's #7: "Why was this decision made?" is one of the most common developer questions. The answer is often in Slack, and now AI can find it.

8. Notion MCP Server — 5,200+ Stars

Notion has become the central hub for team knowledge at many companies. Its MCP server gives AI access to that documentation layer, enabling context-aware assistance that actually knows your team's processes.

Why it's #8: Documentation lives in Notion for millions of teams. AI that can read your runbooks and wikis is dramatically more useful than AI that has to ask you for them.

9. Memory MCP Server — 4,800+ Stars

The Memory MCP server (from Anthropic) provides persistent, cross-conversation memory through a knowledge graph. It lets AI assistants remember facts, preferences, and context across sessions.

Why it's #9: AI forgetting context between sessions is a major usability limitation. Memory MCP solves this with structured, searchable persistence.

10. Fetch MCP Server — 4,500+ Stars

Sometimes you just need your AI to fetch a URL and read it — documentation, API responses, web pages. The Fetch server is the simplest possible web access mechanism, and its simplicity is exactly why it's so widely used.

Why it's #10: The lowest barrier to web access. No API key required, works on any URL, and handles HTML-to-markdown conversion automatically.

Honorable Mentions

  • SQLite MCP Server — The lightweight alternative to PostgreSQL for local databases
  • Supabase MCP Server — Rapid adoption driven by Supabase's developer popularity
  • Firecrawl MCP Server — For structured web scraping at scale
  • EXA MCP Server — AI-optimized semantic web search
  • Linear MCP Server — Popular in engineering-forward teams

The Pattern: What Makes a Popular MCP Server?

Looking at the top 10, a few patterns emerge:

  1. Official servers win — Servers maintained by the original company (GitHub, Anthropic) get more trust and stars
  2. Universal applicability — Servers useful to almost every developer (filesystem, search) dominate over niche tools
  3. Instant ROI — Servers where the benefit is immediately obvious attract faster adoption
  4. Safety-first defaults — Read-only defaults for dangerous capabilities (database writes, file deletion) reduce hesitation to install

Browse the full MyMCPTools catalog — we track all 500+ MCP servers with rankings, installation guides, and real-world use cases.

Related guides:

Recommended Tools

Better Stack

Free Plan

Get alerted when your APIs, browser tests, payment pipelines, or MCP server dependencies go down. Used by 100K+ developers.

Start monitoring free →

1Password

14-day Free Trial

Store and inject API keys, payment credentials, tokens, and file access secrets into your MCP server configs. Trusted by 150K+ developers.

Try 1Password free →

🔧 MCP Servers Mentioned in This Article

📁

Filesystem MCP Server

sandboxed read, write, edit, move and search access to an explicit whitelist of local directories, and it is the reference implementation most other filesystem MCP servers are modelled on. Shipped by Anthropic in the official modelcontextprotocol/servers monorepo (89,000+ stars, actively maintained), it is a Node.js server published to npm as @modelcontextprotocol/server-filesystem. The part worth understanding before you install is the access-control model, because there are now two ways to grant directories and they do not compose. Method one is command-line arguments: `npx -y @modelcontextprotocol/server-filesystem /path/one /path/two`. Method two, and the one the maintainers recommend, is MCP Roots — a client that supports the roots protocol sends its roots at initialization, and those roots COMPLETELY REPLACE any directories passed on the command line, then get replaced again on every `notifications/roots/list_changed`. That means allowed directories can change at runtime without restarting the server, but it also means a roots-capable client silently overrides your CLI arguments. If the server starts with no arguments and the client either does not support roots or sends an empty list, initialization throws an error. The tool surface is broad: `read_text_file` (with mutually exclusive `head`/`tail` line windows), `read_media_file` returning base64 image/audio content blocks, `read_multiple_files` which keeps going when individual reads fail, `write_file`, `edit_file`, `create_directory`, `list_directory`, `list_directory_with_sizes`, `move_file`, `search_files`, `directory_tree`, `get_file_info` and `list_allowed_directories`. `edit_file` is the one to learn — it does line-based and multi-line pattern matching with indentation detection and preservation, returns a git-style diff with context, and supports `dryRun: true` so you can preview a change before applying it; the maintainers recommend always running a dry run first. Every operation is refused outside the allowed set, and `list_allowed_directories` is the fastest way to confirm what the server actually believes it can touch.

Local✓
💻

GitHub MCP Server

authenticated access to the whole GitHub platform — repositories, files, branches, issues, pull requests, Actions runs, security alerts, discussions and notifications — from Claude, Cursor, VS Code, Copilot CLI and any other MCP host. There is no npm package for this server, and that trips up most people who try to install it: `@github/mcp-server` is not published to the npm registry, so any `npx` line you find for it will fail. GitHub ships it three other ways. The easiest is the hosted remote server at https://api.githubcopilot.com/mcp/, which needs no install at all — point an HTTP-transport MCP client at that URL and log in with OAuth (VS Code 1.101+, Claude Desktop, Claude Code, Cursor and Windsurf all support this). The second is the official Docker image ghcr.io/github/github-mcp-server, which is what the copy-paste command on this page runs; on github.com it now performs a browser-based OAuth login on first use and keeps the token in memory only, which is why the published Docker configs map a fixed loopback callback port (-p 127.0.0.1:8085:8085 with GITHUB_OAUTH_CALLBACK_PORT=8085) so the container can receive the callback. Prefer a token? Set GITHUB_PERSONAL_ACCESS_TOKEN instead — it takes precedence over OAuth, and the minimum useful scopes are repo, read:org and read:packages. The third is the native Go binary from the repository's releases, which needs no fixed port for the OAuth flow. GitHub Enterprise Server has no hosted option: use the local server with --gh-host or GITHUB_HOST set to your instance (include the https:// scheme — it defaults to http://, which GHES rejects). Toolsets can be narrowed with GITHUB_TOOLSETS, and an insiders channel is available at /mcp/insiders or via the X-MCP-Insiders header.

Auth required📘✓
🗄️

PostgreSQL MCP Server

The PostgreSQL MCP server was the Model Context Protocol reference server for Postgres, and it is retired: the source now sits in modelcontextprotocol/servers-archived — a repository GitHub reports as archived, described as "Reference MCP servers that are no longer maintained" — and the npm package @modelcontextprotocol/server-postgres carries a deprecation notice reading "Package no longer supported." It still installs and still runs, which is why most third-party setup articles have not caught up. What it provides is deliberately small: a single tool, query, which executes read-only SQL inside a READ ONLY transaction, plus per-table schema information exposed as MCP resources at postgres://<host>/<table>/schema, with column names and data types discovered from database metadata. There is no index advice, no health check, no separate schema-listing tool, and no write mode. Install is npx @modelcontextprotocol/server-postgres with a postgres:// connection string as the argument. For active work against Postgres, the maintained alternative is Postgres MCP Pro (crystaldba/postgres-mcp), which exposes nine tools including index tuning against hypothetical indexes and a database health check, and has an explicit restricted access mode; if your database is hosted on Supabase or Neon, their platform servers add branching and logs that a raw Postgres connection cannot see. Reach for this archived server only when you want the smallest possible surface — one process, one read-only query tool, nothing else.

Local📘✓
🔍

Brave Search MCP Server

The Brave Search MCP Server is the official server from Brave that gives AI assistants privacy-first web search through the independent Brave Search API — no tracking, no profiling, and results drawn from Brave's own web index rather than Google or Bing. It exposes five distinct tools that map directly to the Brave Search API endpoints: brave_web_search for general queries with pagination, freshness filters, and safe-search controls; brave_local_search for businesses, restaurants, and points of interest with automatic location filtering; brave_news_search for recent articles and current events; brave_image_search for image discovery; and brave_video_search for finding videos across the web. Authentication uses a single BRAVE_API_KEY (free tier available at brave.com/search/api) or a mounted BRAVE_API_KEY_FILE for Docker-secret setups. Install in Claude Desktop, Cursor, Windsurf, or VS Code with one npx command and choose stdio or streamable-HTTP transport. Because Brave operates its own crawler and index, the Brave Search MCP server is a strong choice for developers who want an alternative to Google-dependent search tools, need reproducible non-personalized results, or care about data privacy in agent workflows — Claude can pull fresh web context, verify facts, and research topics without leaking queries to ad-tech pipelines.

Local✓
🌍

Puppeteer MCP Server

browser automation over MCP — navigate, click, fill, screenshot and run JavaScript in a real Chromium instance — but the first thing to know is that this server is archived. It was one of Anthropic's original reference servers and now lives in modelcontextprotocol/servers-archived, a repository GitHub reports as archived with no commits since May 2025. The npm package @modelcontextprotocol/server-puppeteer is still installable and still runs, and its last publish is from the same period, so treat it as frozen rather than broken: no new features, no security patches, no dependency bumps on Puppeteer itself. For new work the maintained successors are Microsoft's Playwright MCP server and ExecuteAutomation's Playwright MCP server, both of which cover the same ground with active releases. If you are maintaining an existing integration, the surface is small and easy to reason about. Seven tools: `puppeteer_navigate` (takes an optional `launchOptions` object mirroring PuppeteerJS LaunchOptions — changing it restarts the browser — and an `allowDangerous` flag that must be true before flags like `--no-sandbox` or `--disable-web-security` are accepted), `puppeteer_screenshot` (CSS selector for element shots, 800x600 default, optional `encoded` for a base64 data URI instead of binary content), `puppeteer_click`, `puppeteer_hover`, `puppeteer_fill`, `puppeteer_select`, and `puppeteer_evaluate` for arbitrary JavaScript in the page context. It also exposes two resource types the tools alone do not give you: `console://logs` for the live browser console stream and `screenshot://<name>` for captured PNGs. The README carries an explicit security caution worth repeating — the browser runs on your own machine, so it can reach local files and internal IP addresses, and should not be pointed at untrusted pages while sensitive data is reachable. The npx install opens a visible browser window; the Docker image `mcp/puppeteer` runs headless Chromium instead.

Local
🌍

Playwright MCP Server (ExecuteAutomation)

ExecuteAutomation's Playwright MCP Server is a community-maintained browser automation server (5,500+ GitHub stars) distinct from Microsoft's official microsoft/playwright-mcp — it leans further into test generation and visual workflows rather than pure accessibility-tree navigation. Beyond standard navigate/click/fill/screenshot tools, it can generate Playwright test code from a live browsing session, scrape full page content and structured data, execute arbitrary JavaScript in the page context, and drive API testing (GET/POST/PUT/PATCH/DELETE requests) alongside the browser tools. A standout feature is 143 real device presets for responsive testing — a single call like playwright_resize({ device: "iPhone 13" }) swaps in the correct viewport, user-agent, touch support, and device pixel ratio, and natural-language prompts like "test on iPad landscape" work directly through Claude. Install via `npm install -g @executeautomation/playwright-mcp-server`, Smithery, mcp-get, or the one-line `claude mcp add --transport stdio playwright npx @executeautomation/playwright-mcp-server` for Claude Code; VS Code one-click installers are also published. No API keys are required — it launches and drives a local Chromium/Firefox/WebKit browser directly. Choose this over Microsoft's official server when you specifically need auto-generated Playwright test scripts, JS execution, or device-emulation testing; choose Microsoft's for pure lightweight accessibility-tree page navigation. One maintenance fact the listings omit, checked against GitHub and npm on 2026-08-15: this repository has not been pushed since 2025-12-13 and npm 1.0.12 was published 2025-12-12, with 32 issues open. It is neither archived nor deprecated, so nothing warns you at install time — it installs, connects and works while its Playwright dependency drifts, whereas Microsoft's server ships continuously. Weigh the codegen, 143-preset device emulation and HTTP request tools against running an eight-month-old build. Note also that headless defaults to false on playwright_navigate, so it opens a visible browser window unless told otherwise, and that stdio-mode logging goes only to ~/playwright-mcp-server.log to keep the JSON-RPC stream clean.

Local📘
💬

Slack MCP Server

The Slack MCP server (built by Ivan Korotovsky) connects AI assistants like Claude, Cursor, and Windsurf directly to Slack workspaces, enabling conversational access to your team communication channels without requiring workspace admin approval for a bot install. Its standout feature is a "no permission" stealth mode — it authenticates using your own personal Slack session tokens (xoxc/xoxd, or a stored browser session) rather than requiring a Slack App with OAuth scopes, so it works even in locked-down workspaces where you cannot create bots. It also supports full OAuth Bot Token auth and Enterprise/GovSlack deployments for teams that prefer a conventional app install. Tools exposed include reading channel and DM/group-DM history with smart pagination, searching messages across the workspace, posting messages and thread replies, listing channels and users, and adding reactions. Common use cases include automating standups by posting summaries directly to team channels, searching past Slack conversations to surface decisions or context, monitoring specific channels for keywords or alerts, and drafting replies to thread discussions — all from natural-language prompts. Supports both Stdio and SSE transports plus proxy configuration for corporate networks. Install with: `npx slack-mcp-server@latest --transport stdio`. A separate official-style integration exists from Zencoder (@zencoderai/slack-mcp-server) for teams that prefer standard Bot Token OAuth over session-token auth. Compatible with Claude Desktop, Cursor, VS Code, Windsurf, and Cline.

Local📘
📋

Notion MCP Server

The Notion MCP Server is the official integration from Notion that connects AI assistants directly to your Notion workspace via the Notion REST API. With 4,580+ GitHub stars, it is the canonical MCP tool for bringing Notion's knowledge management capabilities into Claude Desktop, Cursor, Windsurf, and any MCP-compatible client. The server exposes a rich set of tools: search your entire workspace by keyword and return matching pages and databases; retrieve full page content and block trees; create new pages inside any parent page or workspace section; update, append, or delete block content on existing pages; list all databases your integration has access to; query database entries with filter and sort parameters; retrieve individual blocks or nested children by block ID; and add comments to pages. Authentication uses a Notion integration token — create an internal integration at notion.so/my-integrations, share specific pages or databases with it, and set NOTION_TOKEN in your environment (the older OPENAPI_MCP_HEADERS form still works). Install with a single npx command. The Notion MCP Server is especially powerful for AI workflows that span documentation retrieval, project planning, and knowledge capture — Claude can read product specs from Notion, draft new pages from conversation output, log structured data into databases, and search across thousands of notes without any manual copy-paste.

Auth required📘✓
🧠

Memory

Knowledge graph-based persistent memory system. Store and retrieve contextual information.

Local✓
🌐

Fetch

Web content fetching and conversion for efficient LLM usage. Extract readable content from any URL.

Local✓

📚 More from the Blog

Guides

Best MCP Servers for Developers in 2026: The Complete Guide

Discover the top MCP servers that every developer should know about. From filesystem access to database queries, these Model Context Protocol servers supercharge your AI coding workflow.

8 min readGuides

Best MCP Servers for Data Engineering: Database, ETL & Analytics

Top MCP servers for data engineers and analysts. Connect your AI to PostgreSQL, BigQuery, Snowflake, and more for AI-powered data workflows.

7 min readTutorials

Getting Started with MCP: A Beginner's Guide to Model Context Protocol

New to MCP? Learn what Model Context Protocol is, how it works, and how to set up your first MCP server in under 5 minutes. Complete beginner's guide.

10 min read