LinkList — MCP

The best MCP servers in 2026

Nine servers worth connecting, picked by who maintains them and what they expose. Every repository and endpoint on this page was checked on 2026-07-28.

How this list is made

Lists in this category rot: the official reference repository has moved twelve of its original servers — GitHub, PostgreSQL, Slack and Redis among them — into an archive, and pages ranking for this query still recommend some of them as current.

Every entry below names its maintainer, and each was checked on the stated date: repository active, maintainer as claimed, install path as documented. When an entry goes stale, the date will say so.

  1. 01

    GitHub MCP Server

    github.com/github/github-mcp-server · maintained by GitHub · checked 2026-07-28

    Repositories, issues, pull requests, Actions runs and code-security alerts, from inside the agent. Runs two ways: a hosted remote endpoint at api.githubcopilot.com/mcp with OAuth, or locally in Docker with a personal access token. The reference-set GitHub server is archived; this first-party one replaced it.

  2. 02

    Playwright MCP

    github.com/microsoft/playwright-mcp · maintained by Microsoft · checked 2026-07-28

    Drives a real browser: navigate, click, fill forms, read pages. It works from Playwright's accessibility tree rather than screenshots, so it needs no vision model and stays fast. Added with one line: npx @playwright/mcp@latest.

  3. 03

    Filesystem

    github.com/modelcontextprotocol/servers · official reference set · checked 2026-07-28

    Read, write and search files under directories you explicitly allow. Part of the seven-server official reference set, which makes it the most scrutinized implementation of the most common capability.

  4. 04

    Context7

    github.com/upstash/context7 · maintained by Upstash · checked 2026-07-28

    Current, version-specific library documentation pulled into the prompt — against the model's habit of answering from a version two majors old. Two tools; remote endpoint at mcp.context7.com/mcp with a free API key.

  5. 05

    Postgres MCP Pro

    github.com/crystaldba/postgres-mcp · maintained by Crystal DBA · checked 2026-07-28

    The Postgres server to reach for since the reference one was archived. Queries plus what a DBA would want — EXPLAIN-based query analysis, index tuning, health checks — and a restricted mode that holds production access to read-only transactions.

  6. 06

    Notion MCP

    github.com/makenotion/notion-mcp-server · maintained by Notion · checked 2026-07-28

    First-party access to pages and databases: search, read as Markdown, edit, comment. The hosted remote server with OAuth is the maintained path; the open-source local version still works with an API token.

  7. 07

    Fetch

    github.com/modelcontextprotocol/servers · official reference set · checked 2026-07-28

    Fetches a URL and converts the page to model-friendly text. The smallest useful server — and a clean first read if you want to see how one is written.

  8. 08

    Memory

    github.com/modelcontextprotocol/servers · official reference set · checked 2026-07-28

    A knowledge graph the model reads and writes across sessions — entities, relations, observations. Reference-set quality, though what it stores is only as curated as what the model chose to put there.

  9. 09

    LinkList

    linklist.io/mcp · remote, streamable HTTP · checked 2026-07-28

    Disclosure: LinkList publishes this page.

    Citation-grounded retrieval over sources you vetted. Add the documentation you trust to a collection; the agent calls search_sources and every passage comes back with its URL and the date it was fetched. Five tools, three of them read-only. Free key, 100 queries a day, no card.

How many to connect

Every connected server adds its tool schemas to the model's context at the start of a session, so each one has a cost before it is ever called. Three to six servers, chosen for the work at hand, behaves better than a long roster — in context spent, and in the model picking the right tool.

Questions

What happened to the official GitHub and Postgres servers?
The modelcontextprotocol/servers repository moved twelve of its original implementations into an archive, GitHub and PostgreSQL among them. GitHub now maintains its own first-party server, and implementations like Postgres MCP Pro took over the Postgres role. Check the maintainer before trusting an older list.
How many MCP servers should I connect at once?
Few. Tool schemas load into context when the session starts, so every idle server spends context the model could have used for work. Start with the two or three that map to your daily tasks and add on demand.
Do these work with Claude Code, Cursor and Claude Desktop?
Yes — that is the point of the protocol. Local servers need their runtime (Node, Docker or Python); remote ones need a URL and usually a key. Client-by-client setup, verified against a live endpoint, is on the connect pages.
Are MCP servers safe to run?
A server runs with exactly the access you give it: the token you configure, the directories you allow, the database role you connect. Prefer read-only modes and keys where they exist, and keep keys out of files you commit — a key that has reached a repository should be revoked, not deleted from history.

Related

MCP starter pack

Verified setup configs for every client.

Copy-paste configuration for Claude Code, Claude Desktop and Cursor, plus the eval harness so you can measure your own retrieval.

One email with the pack. No sequence.

Point your agent at sources you trust.

LinkList is a remote MCP server: your agent searches the collection you curated and answers with the URL and fetch date attached. Free tier, no card.