npx @modelcontextprotocol/server-postgres-style commands copied around most listicles point at dead packages. Second, a "free" server is only free if the API behind it is — Brave Search, for one, now requires a credit card on file.
MCP (Model Context Protocol) is how AI clients like Claude, Cursor, VS Code, and Copilot plug into your tools — files, Git, browsers, databases, docs. The servers themselves are the cheap part. What follows is what's actually maintained in mid-2026, what quietly broke, and where the $0 stops.
The 7 Reference Servers Still Maintained
The steering group deliberately shrank modelcontextprotocol/servers (89,000+ GitHub stars) to a small educational core. These are the ones still in the repo — all free, all keyless, all runnable in one command:
| Server | What it does | Run it |
|---|---|---|
| Filesystem | Read/write files with configurable access controls | npx -y @modelcontextprotocol/server-filesystem |
| Fetch | Fetch a URL and convert it to LLM-friendly text | uvx mcp-server-fetch |
| Git | Read, search, and manipulate Git repositories | uvx mcp-server-git |
| Memory | Knowledge-graph persistent memory across sessions | npx -y @modelcontextprotocol/server-memory |
| Sequential Thinking | Structured multi-step reasoning scaffold | npx -y @modelcontextprotocol/server-sequentialthinking |
| Time | Current time and timezone conversion | uvx mcp-server-time |
| Everything | Test server exercising every MCP feature | npx -y @modelcontextprotocol/server-everything |
One caveat worth repeating from the repo's own warning: these are reference implementations, meant to demonstrate the protocol and the SDKs — not hardened production services. Filesystem and Git hand an AI agent real write access to your disk, so scope their allowed directories deliberately.
The Archived Trap
This is the part most "free MCP servers" roundups get wrong. Thirteen former reference servers were moved to servers-archived: AWS KB Retrieval, Brave Search, EverArt, GitHub, GitLab, Google Drive, Google Maps, PostgreSQL, Puppeteer, Redis, Sentry, Slack, and SQLite. If a tutorial tells you to run one of those @modelcontextprotocol/server-* packages, it's quoting a snapshot from 2024–2025. Here's where the important ones actually live now:
| Archived server | Use instead | Cost |
|---|---|---|
| GitHub | github/github-mcp-server (official, MIT, 32k★) — or the hosted endpoint https://api.githubcopilot.com/mcp/ | Free with any GitHub account |
| Brave Search | brave/brave-search-mcp-server (official, now v2 with STDIO default) | Card required — see below |
| Puppeteer | Playwright MCP (Apache-2.0, 36k★) or Chrome DevTools MCP (Apache-2.0, 49k★) | Free, no key |
| Slack | zencoderai/slack-mcp-server (community-maintained) | Free with a Slack token |
| PostgreSQL / SQLite / Redis | No official successor — pick a vendor or community server from the MCP Registry | Varies |
The registry is now the canonical place to look — the reference repo's README explicitly redirects there rather than trying to be a directory.
Genuinely Free, No API Key
If your test for "free" is no signup, no card, no quota, this is the set that passes:
- Filesystem, Git, Memory, Fetch, Time, Sequential Thinking — the reference core above. Nothing to authenticate.
- Chrome DevTools MCP — drives a real Chrome for automation, network inspection, console reads, and performance traces. Google-maintained, and the single best "why is my page broken" server.
- Playwright MCP — browser automation via accessibility snapshots rather than screenshots, so it works without a vision model. Note Microsoft's own guidance has shifted: for high-throughput coding agents they now point to the Playwright CLI + skills instead, because MCP tool schemas and accessibility trees eat context. MCP still wins for specialized agentic loops.
- Context7 (MIT, 60k★) — pulls version-specific library documentation into context, which is the cheapest fix for models confidently citing APIs that were removed two releases ago.
Add a local model via Ollama and that entire stack runs at $0 with no account anywhere.
Where "Free" Actually Stops
The server is free; the service it calls may not be. The clearest example, and one most 2026 listicles still get wrong: Brave Search's card-free tier is gone. Per Brave's own pricing page, every plan now requires a credit card on file — Brave describes it as an anti-fraud identity check, not a charge — and instead gives $5 in free credits every month against $5 per 1,000 requests. That's roughly 1,000 free queries a month, not the "2,000 free, no card" figure still circulating.
| Server | Needs a key? | What $0 gets you |
|---|---|---|
| Reference 7 (filesystem, git, …) | No | Unlimited — runs locally |
| Chrome DevTools / Playwright | No | Unlimited — your own browser |
| GitHub | Yes (your own token) | Standard GitHub API rate limits |
| Context7 | Optional | Works keyless on a free rate limit |
| Brave Search | Yes + card on file | $5/month credit ≈ 1,000 queries |
If search is the piece you need free, compare the alternatives in our free search API breakdown before wiring Brave in — and note that post's Brave figures predate this pricing change.
Adding One
Every client reads the same shape. In Claude Desktop it's claude_desktop_config.json; in Cursor and VS Code it's .mcp.json or the workspace MCP settings:
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "/Users/me/projects"]
},
"git": {
"command": "uvx",
"args": ["mcp-server-git", "--repository", "/Users/me/projects/app"]
},
"github": {
"type": "http",
"url": "https://api.githubcopilot.com/mcp/"
}
}
}The trailing path on filesystem is the allow-list — the server can't reach outside it. Restart the client after editing; servers are launched at startup, not hot-reloaded.
What the 2026-07-28 Spec Changed
The 2026-07-28 specification matters mostly if you plan to host a server rather than run one locally. The headline is a stateless protocol core: MCP moves from a bidirectional stateful protocol to request/response, where every request is self-describing, so any request can land on any instance behind a plain round-robin load balancer. Method and tool names now travel in Mcp-Method and Mcp-Name HTTP headers so gateways can route and authorize on headers alone, list responses carry cache hints, and server-to-client calls like sampling and elicitation move to Multi Round-Trip Requests instead of permanently open streams.
For scale context, the MCP team reports its Tier 1 SDKs approaching half a billion downloads a month, with the TypeScript and Python SDKs each past a billion total. Practically: local servers keep working, and remote ones get much cheaper to operate.
Frequently Asked Questions
Are MCP servers free?
The servers themselves are — nearly all are open-source packages you run locally, with no account or quota. Cost enters only through the service a server wraps: a search API, a hosted database, a paid SaaS. A stack of filesystem, Git, memory, fetch, and a browser server is permanently $0.
Why does npx @modelcontextprotocol/server-postgres not work?
Because PostgreSQL is one of the 13 servers moved to servers-archived. The same applies to SQLite, Redis, GitHub, Slack, Puppeteer, GitLab, Google Drive, Google Maps, Sentry, Brave Search, EverArt, and AWS KB Retrieval. Check the MCP Registry for a maintained replacement rather than pinning an unmaintained package.
Do I need a paid Claude or Cursor plan to use MCP?
No. MCP support is a client feature, not a billing tier — Claude Desktop, VS Code with Copilot, Cursor, and several open-source clients all read the same config. You can also drive MCP servers from your own code with any of the official SDKs.
Is it safe to give an AI agent MCP access?
Treat every server as code running with your privileges. The official repo warns plainly that its servers are educational references, not production-hardened. Scope filesystem servers to a single directory, prefer read-only tokens, and remember that a server which fetches web content can pull attacker-controlled text into your model's context.
The Verdict
Free MCP servers are real and abundant — but the ecosystem moved faster than the blog posts describing it. Start from the 7 maintained reference servers plus a browser server and Context7: that's a capable, keyless, genuinely $0 setup. Reach for the registry when you need something specific, check whether the underlying API still has a free tier before you commit, and ignore any tutorial still handing out @modelcontextprotocol/server-github.