Best MCP Servers for Claude Desktop (2026)
Last updated 2026-10-09
Quick answer
The best MCP servers for Claude Desktop in 2026 are Filesystem, GitHub, Memory, Browser Use and Brave Search — depending on what you want Claude to do. Claude Desktop talks to local servers over stdio through claude_desktop_config.json, so the servers below install with one config block and a restart. Start with two or three, not ten.
Top 10 MCP servers for Claude Desktop
Ranked by practical usefulness, not GitHub stars. Free means the MCP server itself is free; connected services may have separate costs.
- ▸Filesystem — read, write and organise local files (free)
- ▸GitHub — repositories, issues, pull requests (free server)
- ▸Memory — persistent structured knowledge across sessions (free)
- ▸Browser Use — drive a real Chrome browser for real tasks (free)
- ▸Firefox DevTools — browser debugging with Mozilla's server (free)
- ▸Fetch — retrieve web page content as clean markdown (free)
- ▸Git — local repository history and changes (free)
- ▸Brave Search — live web search (API limits/pricing)
- ▸Exa — semantic web research for agents (usage-based)
- ▸SQLite — query local database files, read-only by default (free)
How we picked
Claude Desktop was the first MCP client and remains the reference implementation, so the servers that work best there are the ones with clean install steps and identifiable publishers. The registry snapshot behind this directory is community-heavy, so we favoured servers with an active repository and a clear permission story. Two of the ten — Firefox DevTools and Browser Use — are published by the teams behind the browser projects themselves, which is as close to vendor-supported as browser servers get.
For developers, prioritise servers that let Claude actually perform tasks rather than simply retrieve information: file access, repository operations and a real browser close the loop between suggestion and action.
A sensible starter stack
You do not need all ten on day one. Each server adds tools, and every tool spends context window. A practical first three:
- ▸Filesystem, scoped to one project directory — lets Claude read and edit real files
- ▸GitHub — issues, pull requests and code search without leaving the chat
- ▸Brave Search or Fetch — one server for fresh, citable web facts
How to install them
Every server on this list connects through Claude Desktop's config file: Settings → Developer → Edit Config, then paste the server's mcpServers JSON block and restart the app. Each server page in this directory shows a copy-paste config block — for example the Filesystem server page has the exact JSON with safe directory scoping.
Full walkthrough: Claude Desktop MCP setup guide.
Safety notes
Filesystem and Git servers can change your machine. Scope Filesystem to the single project directory you are working in — never your home folder. Start GitHub with read-only scopes and keep a human in the loop for merges and pushes. Browser servers (Browser Use, Firefox DevTools) can see whatever the browser can, including logged-in sessions; use a dedicated browser profile. The MCP security guide covers the full checklist.
The picks, one by one
Sandboxed local file access with document parsing — read, write and organise files inside directories you allow.
Best for: Letting Claude work on real project files instead of pasting code into chat.
Watch out: Scope it to one project directory, never your home folder.
GitHub via MCP: repos, issues, pull requests, file reads and notifications, with OAuth device flow or token auth.
Best for: Developers triaging issues and reviewing PRs without switching tabs.
Watch out: Can write to repositories — start with read-only scopes.
Persistent memory vault shared across your MCP clients over OAuth.
Best for: Long-running projects where context must survive restarts.
Watch out: Only as accurate as what was stored — prune it.
Mozilla's Firefox DevTools server attaches to a live tab — console errors, network, screenshots, profiling.
Best for: Debugging web apps with real telemetry instead of pasted stack traces.
Watch out: Same session-visibility caveat as any browser server.
HTTP fetch with SSRF protection that converts pages to clean markdown.
Best for: Reading a specific page or doc on demand.
Watch out: No search — pair it with Brave Search for discovery.
Local Git operations: status, diffs, history, branches and gated stage/commit.
Best for: Inspecting and committing to local repos with Claude's help.
Watch out: Push and history rewriting deserve a human review.
Live web search over an independent index, returning fresh citable results.
Best for: Facts the model cannot know: news, prices, recent releases.
Watch out: Requires a Brave API key with monthly free tier limits.
Neural web search and content fetch — find pages by meaning, not keyword.
Best for: Research queries where keyword search misses.
Watch out: Usage-based pricing beyond free credits.
SQLite over MCP with read-only defaults, row caps and statement timeouts.
Best for: Asking questions of local database files and exports.
Watch out: Single-file scope — that is the safety feature.
Frequently asked questions
How many MCP servers should I run in Claude Desktop at once?＋
Start with two or three. Every server adds tools to Claude's context, which costs window space and can confuse tool selection. Add more only when a real task needs them.
Do these servers cost money?＋
The servers themselves are free and open source. Some connect to paid APIs — Brave Search has a free tier with monthly limits, and GitHub is free against GitHub's own rate limits.
Where does Claude Desktop's config file live?＋
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json. Windows: %APPDATA%\Claude\claude_desktop_config.json. Open it from the app via Settings → Developer → Edit Config.
Which of these servers are vendor-published?＋
The Firefox DevTools server is published by Mozilla and Browser Use by the Browser Use project; the rest are community or independent-maintainer servers. MCP servers are third-party by nature — check each repository before connecting.