Best MCP servers
for Claude in 2026
Every "best MCP servers for Claude" list I've read so far has the same problem. It's written by someone who hasn't used any of them. You get alphabetical lists, GitHub star counts, and feature bullets copied from READMEs. None of it tells you which ones survive past the first week.
So this is the other kind of list. The MCP servers I actually have installed in Claude right now, what each one earns its spot for, and a few I tried and removed. If you're new to Model Context Protocol, the one-line version is that MCP lets Claude reach outside the chat window and call real services. Filesystems, databases, your calendar, your finance tracker. Each server adds one capability. The art is knowing which ones to bother with.
How I decide whether a server is worth keeping
Three quick questions before installing anything.
First, does this actually remove a context switch? A lot of MCP servers just put a thin wrapper around a UI I'd open anyway. If I still need to tab over to the app to verify, finish, or correct what Claude did, the server is adding friction, not removing it.
Second, are the tool descriptions tight enough that Claude will reach for them? Claude has to pick from whatever's installed. Servers with vague tool names, fifteen near-identical parameters, or overlap with built-in capabilities tend to sit there unused. You'll notice after a week that you never said anything that triggered them.
Third, local or remote? Local servers run on your machine over stdio. Remote servers run over HTTP with OAuth. Local is great for filesystem and private data. Remote wins the moment you want the same data on a phone, a second laptop, or shared with another person.
The developer set
This is where MCP currently shines. If you write code, the payback is immediate.
Filesystem
The one server I'd install first on a new machine. Refactor across files, search code without remembering grep flags, ask Claude to write a test that mirrors the patterns already in the repo. Pays for itself inside an hour.
GitHub
Issues, PRs, code search, comments. The workflow I use most is reviewing a PR in conversation, getting Claude to summarize the diff, then dispatching a couple of follow-up tickets without ever opening the GitHub tab. Works best paired with Filesystem so Claude can read the actual code under review, not just the patch.
PostgreSQL or SQLite
Query a real database in plain English. The official Postgres server defaults to read-only, which is the correct default. "How many users signed up last week, grouped by referrer" stops being a five-minute SQL session and becomes a one-line question. I'd never let it write, but for read queries it's a huge win.
Sentry
Pulls issue details and stack traces into the conversation. Replaces the "open Sentry, copy the trace, paste into chat" loop that everyone has and nobody enjoys. Pair with Filesystem and Claude will often propose a real fix, not a guess.
Linear
Create and update issues, list assignments, query by project. The combination I like is GitHub plus Linear: "summarize this PR and open a Linear ticket for the bug we noticed in passing." Only useful if your team is already disciplined about issue hygiene. If Linear is a graveyard, this won't help.
Productivity and knowledge
Notion
Useful for retrieval, less useful for authoring. Notion's block model doesn't map cleanly to plain text, so anything Claude creates tends to need a quick cleanup pass. I mostly use it for "find the spec we wrote three months ago" rather than as a writing surface.
Gmail and Google Calendar
Calendar is the big one. "Find an hour next week when both of us are free" works without ever opening the app. Gmail is solid for searching threads and drafting first passes I'll revise. I don't let it send unsupervised, partly out of caution, partly because text that sounds slightly off in email is worse than no email at all.
Slack
Best for "what did the team decide about X last Tuesday" without scrolling. Posting from Claude works fine technically. I do it sparingly because messages that sound a touch off in Slack read as bot traffic, and that erodes trust faster than it saves time.
Finance
The finance category is the one where the MCP ecosystem feels genuinely new. There's no incumbent "everyone uses this" tool yet, and the architectural choices vary a lot. Worth knowing the main options before you pick.
YNAB MCP
If you already pay for YNAB, an MCP server gets you ask-anything access to your budget. "How much did I spend on groceries last month?" or "Walk me through reconciling this account" in plain English. Several community implementations exist (calebl, jsclayton, and others). All wrap the YNAB REST API. Only useful if you actually run YNAB.
Actual Budget MCP
Actual Budget is a free, open-source budgeting app you self-host. The Actual MCP server exposes accounts, transactions, and budget categories to Claude, so you can do spending analysis or category review in chat. Good fit if you already run Actual and want a conversational layer on top.
Monarch Money MCP
Wraps Monarch's API to expose accounts, transactions, budgets, and subscription tracking. The richest data of any finance MCP because Monarch aggregates from your bank via Plaid. The trade-off is the standard one: you're trusting Plaid with bank credentials. Good if you already use Monarch and want Claude to summarise what's there.
Lunch Money MCP
Lunch Money is a developer-friendly budgeting tool with a clean API. The community MCP server exposes transactions, budgets, and tagging. Comfortable choice for technical users who already prefer Lunch Money's no-nonsense interface.
Kachink
The MCP-native option. Unlike the servers above, Kachink isn't a
wrapper around an existing app's API. It's built from scratch as a
remote MCP server, so the chat IS the interface. Log expenses in
plain English ("paid 450 THB for lunch"), set up recurring
transactions, query monthly totals, view an interactive dashboard
rendered as an MCP App right inside
Claude. No standalone app, no bank sync, no Plaid. Free for personal
use, one URL to install: https://kachink.app/mcp.
Quick way to pick between them: already paying for YNAB or Monarch? Use their MCP server. Running Actual or Lunch Money? Same. Don't have a finance tool yet and want one that's MCP-first? That's where Kachink fits.
Web and research
Fetch
Grab a URL and turn it into clean markdown Claude can read. Useful when you want to discuss one specific page rather than trust Claude's general web search to find the right thing. Pair with a search server for the full research loop.
Brave Search or Exa
Direct search APIs with structured results. Worth installing if you do a lot of research and care about consistent retrieval quality across sessions. The free tiers are plenty for personal use.
What I'd skip
Not every server is worth installing, even free ones. A few patterns I've learned to recognise.
Servers that duplicate Claude's built-in capabilities. Claude can already do basic web search and run code in a sandbox. An MCP server that "lets Claude search Google" usually just adds a slower path to something Claude was doing fine already.
Servers with fifty tools. Claude picks from whatever's exposed, and a server that maps every single API endpoint as a separate tool dilutes itself. Quality of tool descriptions matters more than how many tools are listed.
Servers with vague tool names. If I can't tell what a tool does from its name and description, Claude probably can't either. It just sits there unused.
Local-only servers for things I want across devices. I tried a local SQLite finance tracker before building Kachink. It was fine until I switched laptops and realised half my data was on the old one. Remote with OAuth is worth the slightly fussier setup.
If you're starting from zero
The smallest set that pays back fastest, in my experience: Filesystem for code, Fetch for reading specific pages, Calendar for scheduling, and Kachink if you track expenses. Four servers, and they cover most of the wins you'll feel day to day. Add more later when you notice an actual gap, not because the directory says you should.
Where to find more
The official MCP registry, PulseMCP, Glama, and MCP.so all maintain server catalogues. They're good for discovery, less good for judging whether a server is any good. The honest signal is "what do people still have installed a month later." For that, r/ClaudeAI and the MCP Discord are more reliable than any directory.
If you want to go deeper on how MCP actually works, the what is MCP explainer walks through the protocol. The track-expenses guide shows what a daily conversational workflow with one of these servers looks like in practice.
Common questions
It's a small program that exposes tools and data to an AI assistant. When you install one in Claude, the assistant gains the ability to do whatever that server is for: read your files, query a database, log an expense, search a website. The protocol that makes this work is open and shared across vendors, so the same server can be used by different AI clients.
Fewer than you'd think. Four to six well-chosen servers covers most daily wins. Past that you start to dilute Claude's ability to pick the right tool, and you start forgetting which servers do what. Add new ones when you notice a specific gap, not because a directory has lots of them listed.
Most are free. A few wrap paid APIs (search providers, some commercial SaaS connectors) and pass through the cost, so you pay whatever that service charges. Anthropic's official servers are free. Kachink is free for personal use.
The protocol itself is documented at modelcontextprotocol.io. For a non-technical walkthrough, we wrote a what-is-MCP guide that explains the moving parts without code. Read our MCP explainer
Add the finance server to your set
If you're already running a couple of MCP servers, adding Kachink takes 30 seconds. Log expenses in plain English, see them on a dashboard inside Claude.
https://kachink.app/mcp