Best MCP servers for developers in 2026: a practical guide

Anthropic archived their flagship reference MCP servers — GitHub, PostgreSQL, Slack, GitLab, Google Drive, SQLite — on May 29, 2025. The servers worth using in 2026 are all third-party. Microsoft’s Playwright server has more GitHub stars than any Anthropic project ever did. GitHub shipped their own Go-based implementation. Stripe, Supabase, and Neon have official servers that connect via OAuth — no key management required beyond the first setup.

Here’s what’s production-ready, ranked by adoption signal and real-world utility.

Who this is for

Developers integrating Claude Code, Claude Desktop, or Cursor with external services through the Model Context Protocol. If you want to build your own server instead, How to build an MCP server covers that separately. For a comparison of MCP versus REST APIs, see MCP vs REST: when the protocol wins.

How we evaluated

GitHub star counts as of mid-2026. Setup complexity rated 1–3: 1 = copy-paste a config block; 2 = API key or OAuth plus a config block; 3 = self-hosted or non-trivial local install. Free-tier data from provider pricing pages, verified June 2026. We confirmed each server is MCP-compliant with a commit within 60 days of publication.

Server comparison

Server	Category	Free tier	Claude	Cursor	Affiliate
GitHub MCP	Code / DevOps	Free (API rate limits)	Yes	Yes	No
Playwright MCP	Browser automation	Free (local compute)	Yes	Yes	No
Stripe MCP	Payments	Free (Stripe API limits)	Yes	Yes	No
Supabase MCP	Database + BaaS	2 projects, 500 MB DB	Yes	Yes	Yes
Neon MCP	Serverless Postgres	100 projects, 100 CU-hr/mo	Yes	Yes	Yes
Cloudflare MCP	Cloud infra	100K Workers req/day	Yes	Yes	No
Linear MCP	Issue tracking	Free with Linear Free	Yes	Yes	No
Filesystem MCP	Local files	Free	Yes	Local only	No

GitHub MCP server

Stars: ~28,600 (github/github-mcp-server) — Setup: 2 — Hosted: remote

GitHub’s official server, written in Go, covers the full repository surface: pull requests, issues, code search, GitHub Actions, file contents, commits, branches, and release management. Remote-hosted — no local binary to install. Connects via a personal access token scoped to exactly the permissions you grant.

Real use case: reviewing an open PR without leaving Claude Code. Ask Claude to summarize the diff, list open review comments, check the failing CI step, and draft a reply to a specific thread. The server handles pagination and API calls; you stay in one context.

Config:

{
  "mcpServers": {
    "github": {
      "type": "http",
      "url": "https://api.githubcopilot.com/mcp/"
    }
  }
}

Pricing: free. Standard GitHub API limits apply: 5,000 requests per hour for authenticated calls.

Microsoft Playwright MCP

Stars: ~33,700 (microsoft/playwright-mcp) — Setup: 2 — Hosted: local

The highest-starred MCP server in the ecosystem by a wide margin. Playwright MCP drives real Chromium through the browser’s accessibility tree — not screenshots. This matters: because the server returns structured accessibility data instead of pixel images, it works with any Claude model, not just vision-capable ones. The actions are precise (click by accessibility role and name, not by screen coordinates) and deterministic.

Real use case: E2E test authoring without writing code first. Describe the user flow in plain English; the server navigates a real browser, extracts structured results, and surfaces failures as JSON. Then use Claude to convert the session log into a Playwright test file.

Setup:

npx @playwright/mcp@latest

First run downloads Chromium. Add the resulting path to your MCP config. The server starts on demand — no persistent process.

Pricing: free. Compute is local.

Stripe MCP

Stars: N/A (official remote server, not a repo) — Setup: 2 — Hosted: remote (mcp.stripe.com)

Stripe’s official remote MCP server connects to your live or test account via OAuth or a scoped restricted key. Permission-aware by design: a read-only key exposes only read tools; a restricted key exposes exactly the operations you scoped in the Stripe dashboard. You cannot accidentally trigger a refund with a key that doesn’t have refund scope.

Real use case: “Show me all failed payments from the last 7 days, group by decline code, and draft a plain-English summary I can paste into Slack.” The server handles pagination and structured data return; Claude does the grouping and writing.

Config (Claude Desktop remote server):

{
  "mcpServers": {
    "stripe": {
      "url": "https://mcp.stripe.com",
      "transport": "sse"
    }
  }
}

Pricing: free. Stripe’s standard API rate limits apply.

Supabase MCP

Stars: tracked via supabase/mcp-server-supabase — Setup: 2 — Hosted: remote

Supabase’s official server connects Claude to a specific Supabase project: Postgres queries, edge function invocations, storage bucket operations, and Auth user management. Authorization is project-scoped — the server only touches what you explicitly authorized.

The practical value is debugging without context-switching. When something breaks in production, you can query the live database, check Auth logs, test an RLS policy, and confirm the fix — without opening a browser tab or a separate database client.

Real use case: “Find the user record where last_sign_in_at is null but created_at is more than 30 days ago, check if there’s an Auth log entry for them, and show me the RLS policy on the profiles table.” That query normally requires three separate tools. Here it’s one prompt.

Pricing:

Free: 2 active projects, 500 MB database per project, 1 GB file storage
Pro: $25/month per organization (8 GB database, daily backups, no project pausing)

If you’re not on Supabase: Supabase Pro

Neon MCP

Stars: tracked via neondatabase/mcp-server-neon — Setup: 1 — Hosted: local or remote

Neon’s server is the cleanest Postgres-focused integration in this roundup. It exposes database branching as a first-class MCP tool — you can create a branch from main, run migrations against it, validate the schema, and drop the branch or merge it, all from a single Claude prompt. That removes the entire manual branch lifecycle from migration workflows.

Storage cost dropped roughly 80% post-Databricks acquisition in early 2026. The free tier is now meaningfully useful: 100 active projects and 100 compute-unit hours per month.

Real use case: “Create a branch from main, apply this migration file, run a count query on the new table to confirm it populated correctly, then show me the schema diff between branch and main.” One prompt — no branch creation UI, no connection string copy-paste, no cleanup.

Config: connect via the Neon MCP remote URL in your project dashboard. One OAuth authorization, then the server is available in Claude Desktop and Cursor.

Pricing:

Free: 100 active projects, 100 CU-hr/mo, 0.5 GB storage
Launch: usage-based (compute $0.106/CU-hr, storage $0.35/GB-month; billed monthly, no minimum)

If you’re not on Neon: Neon Launch plan

Cloudflare MCP

Stars: ~3,800 (cloudflare/mcp-server-cloudflare) — Setup: 2 — Hosted: local or remote

Cloudflare’s server exposes 2,500+ API endpoints via two meta-tools: one for executing API calls and one for searching Cloudflare’s developer documentation inline. That covers the entire Cloudflare surface — Workers, KV, D1, R2, DNS, Pages, Queues, AI Gateway — from a single server.

Real use case: “Deploy this Worker script, bind it to an existing KV namespace, add a DNS route pointing api.yourdomain.com to it, and confirm the route resolves.” Four operations across two Cloudflare products, executed from one prompt without touching the dashboard.

Setup:

npx @cloudflare/mcp-server-cloudflare

Requires a Cloudflare API token. The wrangler login flow generates one.

Pricing:

Workers free: 100,000 requests/day
Workers Paid: $5/month (10 million requests included)

No content affiliate for Cloudflare (B2B partner program only — the recommendation here is on merit).

Linear MCP

Stars: N/A (official remote server) — Setup: 1 — Hosted: remote (https://mcp.linear.app/sse)

Linear’s official remote server. Connects via OAuth to your workspace. Covers the core workflow surface: creating and updating issues, querying by filter or assignee, managing cycles, reading projects, and adding comments.

Real use case: “Create a bug report for the login redirect regression, assign it to me, set priority High, add it to the current cycle, and link it to the Q2 milestone.” That’s normally four clicks across two sidebar panels. Here it’s one prompt.

Config:

{
  "mcpServers": {
    "linear": {
      "url": "https://mcp.linear.app/sse",
      "transport": "sse"
    }
  }
}

Pricing: free with Linear’s Free plan.

Filesystem MCP

Stars: N/A (Anthropic reference server — still active) — Setup: 1 — Hosted: local

The one Anthropic reference server still in active use. It gives Claude sandboxed read/write access to a directory you define at startup. Nothing escapes the configured root path. Supported operations: read file, write file, list directory, search by filename glob, move and delete.

Use this as the first server you configure — it validates that your MCP setup is working before you add anything remote. It’s also useful for giving Claude access to a local docs folder or a config directory without exposing your entire filesystem.

Config:

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/sandbox"]
    }
  }
}

Pricing: free.

Verdict

For most developers, the essential starting stack is three servers: GitHub MCP for code and PR workflows, Playwright MCP for browser automation or E2E testing, and either Supabase MCP or Neon MCP depending on which database you’re already on.

Add Stripe MCP if your product handles payments — the scoped permissions model alone is worth the setup. Add Linear MCP if your team is on Linear. Install Filesystem MCP first to confirm your MCP configuration works before layering in remote servers.

Skip the archived Anthropic servers (postgres, slack, gitlab, google-drive, sqlite). They still appear in some registries but are not maintained.

Discovering new servers

The MCP Registry at modelcontextprotocol.io is the catalog for third-party servers — roughly 200 verified entries as of mid-2026, filterable by category and compatibility. Authentication via GitHub OAuth. Star count on GitHub is an adoption signal, not a quality signal: the Filesystem server is one of the most-used servers in the ecosystem and has few stars because Anthropic ships it as a reference rather than a marketed product.

For building your own server, see How to build an MCP server and How to build MCP tools for Cursor.

Caveats

Star counts are mid-2026 snapshots; they will drift. Supabase and Neon pricing verified from provider pages, June 2026. Cloudflare Workers limits from developers.cloudflare.com, June 2026. PlanetScale MCP was not confirmed from primary sources and is not included. Slack MCP (archived by Anthropic) may have an active community fork — not included without confirming current maintenance status.

Who this is for

How we evaluated

Server comparison

GitHub MCP server

Microsoft Playwright MCP

Stripe MCP

Supabase MCP

Neon MCP

Cloudflare MCP

Linear MCP

Filesystem MCP

Verdict

Discovering new servers

Caveats

References