Forum · Articles

Top 8 MCP servers worth installing for Claude (2026)

By Quang Hieu ·

"If you had to recommend just 3–5 MCP servers, which ones would you pick and why?" That is the question one person asked on r/mcp, and it keeps coming back in other forms: what's the best MCP server you've used, which ones do you really use, and on r/ClaudeAI, which servers are actually useful, because I'm tired of fake lists.

So here is a short list, not a long one. An MCP server gives your AI a new tool: a browser, a repo, a database. Each one below is open source, free to install, and has a public repo you can read before you trust it. For each server you get what it does, who it is good for, and one real catch. Nothing here is a benchmark; the order follows how often the same names came up in those threads.

1. Context7 MCP

Context7 MCP (MIT, by Upstash) pulls current library documentation and code examples into the chat, for the version you are on. It stops the model from writing code against an API that changed two releases ago.

Good for: anyone who writes code with Claude against fast-moving frameworks.

The catch: it fetches docs over the network, so it needs a connection. In Claude Code it declares no allowed tools, so Claude asks for permission each time it calls it.

2. Playwright MCP

Playwright MCP (Apache-2.0, by Microsoft) lets your AI open pages, click, fill forms and read a page through the accessibility tree, in a real browser.

Good for: checking a web app you are building, filling repetitive forms, reading pages that need a login.

The catch: the first run has to install the Playwright browsers, which is a sizeable download.

3. GitHub MCP server

GitHub MCP server (MIT, by GitHub) is the official server for reading repos, opening and reviewing pull requests, and managing issues and Actions from your AI.

Good for: developers who live in GitHub and want the agent to file issues or review PRs.

The catch: it needs a GitHub token, and whatever that token can do, the agent can do. Give it the smallest scope you can.

4. Chrome DevTools MCP

Chrome DevTools MCP (Apache-2.0, by the Chrome DevTools team) lets your AI drive a real Chrome with DevTools: performance traces, network requests, console output and screenshots.

Good for: debugging a slow page or a failing request by asking, instead of clicking through tabs.

The catch: it needs Chrome installed on the same machine.

5. Firecrawl MCP Server

Firecrawl MCP Server (MIT, by Firecrawl) scrapes, crawls and searches the web and hands back clean markdown. A keyless hosted endpoint is available.

Good for: research tasks where the AI has to read many pages, not just one.

The catch: the keyless tier has a usage limit. When we gathered the Reddit questions for this article, it stopped answering after two searches. For regular use you need your own key.

6. Exa MCP Server

Exa MCP Server (MIT, by Exa Labs) is hosted web search and page fetching built for AI agents, with nothing to install locally.

Good for: giving Claude search results that point to source pages rather than SEO filler.

The catch: it needs an Exa API key.

7. Notion MCP server

Notion MCP server (MIT, by Notion) is Notion's official server: search, read and edit pages and databases in your workspace.

Good for: teams whose notes, plans and content calendars already live in Notion.

The catch: it needs a Notion integration token, and it only sees the pages you have shared with that integration. If a page seems missing, share it first.

8. Postgres MCP Pro

Postgres MCP Pro (MIT, by Crystal DBA) connects your AI to a Postgres database, with health checks, index tuning and explain plans, plus a restricted read-only mode for production.

Good for: asking plain-English questions about your data, or finding the slow query.

The catch: an agent with write access to a database can change data. Start with a read-only database user and the restricted mode.

How to pick three

Most people in those threads run a handful, not dozens. Each server adds tools the model has to choose between, and more choice means more wrong calls. A simple start:

  1. One for docs — Context7 if you write code.
  2. One for the browser — Playwright for general pages, Chrome DevTools for debugging your own site.
  3. One for where your work lives — GitHub, Notion or Postgres.

Add a search server (Firecrawl or Exa) only when you notice yourself pasting web pages into the chat by hand.

To add any of these, open the item page and follow the install steps, or read how to install a skill for the general flow. Before you hand a server a token, read its repo: you are giving the AI the same access you have.

More from the blog