Claude Code ships blind — no context gauge, no quota counter. I built a 7-segment statusline and baked in a 50% context handoff rule, backed by Lost-in-the-Middle research. Every segment, every color rule, and the full production script explained.
Intelligence isn't about what you know — it's about how you interact with the world. That one insight explains why AI is growing up in exactly the same order as a human child, and doing it a million times faster.
70 prompt tips for Claude Code are floating around. 7 actually moved the needle for me. Real before/after terminal sessions, a copy-paste cheat sheet, and the 3 patterns I dropped.
I tested 12 MCP servers for Claude Code over three months. 5 earned a permanent spot, 7 got removed. The short list for non-programmers, with real usage frequency and a copy-paste .mcp.json.
TL;DR
.mcp.jsonEvery week I get a version of the same question about Claude Code MCP:
"I keep seeing MCP everywhere. Is it actually worth setting up for Claude Code? I'm not a programmer — I just write and do research. Do I need this?"
The short answer is: yes, but only 5 of them, and only if you know what job you want them to do. The long answer is this post.
Most "best MCP servers for Claude Code" articles assume you're building software. I'm not, and maybe you aren't either. My Claude Code session is about drafts, notes, research folders, and the occasional GitHub issue — not a Kubernetes cluster. That's the setup I'm describing here.
If you haven't set up your CLAUDE.md and your first few Skills yet, go there first — MCP is the third layer of extensions you should touch, not the first.
Otherwise, jump ahead: The 5 I Keep, The 7 I Dropped, or The Copy-Paste Config.
Short answer: MCP (Model Context Protocol) is a standard way for Claude to connect to external tools and services. Think of it as a USB-C port — one plug, many devices.
Before MCP, if you wanted Claude to read your Notion pages, someone had to build a custom integration. If you wanted it to query your database, another integration. If you wanted web search, yet another. MCP collapsed all of that into a single standard: any tool that speaks MCP can talk to Claude Code, Claude.ai, Claude Desktop, or any other MCP-aware client.
The practical shape: an MCP server is a small program that runs on your machine (or sometimes remotely), exposing a set of tools Claude can call. You tell Claude Code about it once in a config file, and Claude now has a new capability — like "search the web" or "read files outside your current folder."
Anthropic's docs and the MCP project site are the source of truth if you want the formal spec. For the rest of this post, the working definition is: MCP = Claude's plugin system.
This is the single most asked question I see, and most answers dodge it. Here's the one that's worked for me.
| If the thing you need is… | Use… |
|---|---|
| An action Claude should take using existing tools (a prompt pattern with a specific goal) | Skill |
| An external service Claude doesn't currently know about | MCP |
| Rules and conventions (voice, style, naming) | CLAUDE.md |
Examples, concrete:
A Reddit thread I see cited often takes a stronger position: "Don't use MCP. Use skills. You are eating up your context." That's overstated. The real rule is: don't use an MCP when a Skill would do. MCPs cost startup context for every tool they expose; Skills cost nothing until invoked. Reach for the cheaper one first.
Ranked by how often I actually use them in a normal work week. All five are free, open-source, and work for non-developer use cases.
What it does: Gives Claude real-time web search through Brave's independent index. Requires a free API key from brave.com/search/api — the free tier covers 2,000 queries a month and takes under a minute to set up.
Why I keep it: Every article I write needs source-checking. Before this, I'd leave Claude, open a browser, search manually, copy URLs back. Now Claude does it mid-thought, gets the URL, and keeps going. A single research session can fire this 10-15 times without me noticing.
Install:
claude mcp add brave-search --scope user --env BRAVE_API_KEY=your_key -- npx -y @modelcontextprotocol/server-brave-search
Honest caveat: If you burn through the 2,000-query monthly free tier, Brave has paid plans starting around $5/month. I've only crossed that ceiling in one week of heavy research work.
What it does: Pulls up-to-date documentation for any library, framework, or CLI tool straight into Claude's context. If I write "how do I do X in Claude Code?" or "what's the latest Next.js API for Y?", Context7 hands Claude the current docs instead of its training-data version.
Why I keep it: My training-data-cutoff fear goes away. When I'm writing technical content about tools that update monthly (Claude Code itself, Next.js, Prisma), Context7 guarantees Claude is answering from now, not from March 2024.
Install:
claude mcp add context7 --scope user -- npx -y @upstash/context7-mcp
Honest caveat: Works best when you're specific. "How does Next.js handle X?" is better than "tell me about Next.js."
What it does: Extends Claude's file access beyond the single directory it was launched from. Lets it read and write files across a set of folders you approve.
Why I keep it: My content workspace is one project. My notes are in another. My templates are in a third. Without Filesystem, switching between them means restarting Claude in each directory. With it, Claude can read a template from ~/templates/, pull research from ~/research/, and write output to ~/articles/current/ — all in one session.
Install:
claude mcp add filesystem --scope user -- npx -y @modelcontextprotocol/server-filesystem ~/articles ~/research ~/templates
Substitute the paths for your own folders. Only list folders you're comfortable with Claude reading and writing.
Honest caveat: This expands the blast radius of any mistake. Claude can now rename files across your whole setup, not just one project. Stage changes with git add frequently (the stage-then-continue pattern from the prompts post matters more than ever here).
What it does: Persistent memory across sessions, beyond what Auto Memory already does. A user on r/ClaudeAI built an open-source memory MCP that claims 80% context token savings for long-running projects; the official reference implementation is simpler but still meaningful.
Why I keep it: Auto Memory is good but opaque — you can't always tell what Claude saved. A Memory MCP gives you explicit, inspectable storage. I use it for project-level context that outlives any single session: "this book project targets X audience, with Y sources already read."
Install:
claude mcp add memory --scope user -- npx -y @modelcontextprotocol/server-memory
Honest caveat: If you're already happy with Auto Memory, you may not need this. It's the most skippable of the five.
What it does: Lets Claude open, search, and comment on GitHub issues and PRs; fetch file contents from any public repo; view commit history.
Why I keep it: My articles live in a private GitHub repo. My templates are in a public one. Sometimes I want Claude to pull the latest README from a tool I'm writing about. Sometimes I want it to file an issue on my own project. GitHub MCP handles both.
Install:
claude mcp add github --scope user --env GITHUB_PERSONAL_ACCESS_TOKEN=your_token -- npx -y @modelcontextprotocol/server-github
You'll need to create a GitHub personal access token and paste it in place of your_token.
Honest caveat: If you don't use GitHub actively, skip this one. It's mid-tier on this list because most non-programmers don't.
Seven cuts, with reasons.
| MCP | Why I tried it | Why I dropped it |
|---|---|---|
| Playwright MCP | Wanted Claude to scrape web pages | Claude running Playwright directly via the CLI is widely reported to be more reliable. I agree. |
| Puppeteer | Same goal | Same outcome. Overlap with Playwright anyway. |
| Figma | Tried it when planning a site redesign | I don't design enough to earn the context overhead |
| Slack | Thought team chat sync would be useful | I'm a one-person operation; no Slack worth integrating |
| PostgreSQL | Curious to see it work | I don't have databases in my workflow |
| Stripe | AWP uses Stripe for membership | The Stripe dashboard is 30 seconds away and safer for financial ops |
| Gmail | Wanted draft emails summarized | Real security concerns + the web UI is faster for me in practice |
Pattern I noticed after the fact: every MCP I dropped was for a service I thought I wanted automated but actually preferred to handle in its own UI. Financial tools. Design tools. Team chat. The ones that stuck are the ones where the target is text or files — where Claude adds something beyond what a web dashboard provides.
This is the hidden cost nobody talks about.
Every MCP server registers its tools at session startup. Each tool description loads into context. If you have 10 MCPs, each exposing 5 tools, that's 50 tool descriptions in your system prompt every single session — whether you use them or not.
A 2026 Reddit thread flagged this for Skills; the same principle applies more acutely to MCPs because their descriptions are usually richer. A friend of mine had 18 MCPs installed and was losing 12% of his context to tool descriptions before a single message was sent.
Practical rule: Keep your MCP count under 7. Audit monthly. If a server hasn't been called in 30 days, remove it. You can always add it back.
Yes. Three cases, specifically:
I went four months without any MCP. I didn't miss them. I added them when specific pain points (manual web searches, scattered folders) actually showed up. That sequencing still seems right.
Claude Code 0.5+ has the claude mcp command. The basic flow is three lines:
# 1. Add the server
claude mcp add <name> --scope user -- npx -y <package>
# 2. Verify it loaded
claude mcp list
# 3. Remove it if you change your mind
claude mcp remove <name> --scope user
What --scope user does: makes the server available in every project you open. The other option is --scope project, which only loads it for the current folder and commits to the project's config. I use user for anything general (Brave, Context7) and project for anything tied to a specific repo (project-specific GitHub tokens, for instance).
What to check after install:
/context to see that tools are registered (no errors, expected tool names present)If something breaks: the MCP server is a process on your machine. claude mcp list will tell you if it's connected. If not, restart the session, or reinstall. 90% of MCP "failures" are just the server crashing and needing to be relaunched.
If you prefer editing config files directly, paste this into ~/.claude/.mcp.json. It's the 5-server baseline I recommend.
{
"mcpServers": {
"brave-search": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-brave-search"],
"env": {
"BRAVE_API_KEY": "your_key_here_or_leave_empty_for_free_tier"
}
},
"context7": {
"command": "npx",
"args": ["-y", "@upstash/context7-mcp"]
},
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"/Users/you/articles",
"/Users/you/research",
"/Users/you/templates"
]
},
"memory": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-memory"]
},
"github": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-github"],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "your_token_here"
}
}
}
}
Replace the paths and tokens. Restart Claude Code. Done.
Most of the popular MCP servers are published as npm packages, so yes — you'll need Node installed. It's a one-time setup. Download from nodejs.org if you don't have it. Some MCP servers ship as Python packages or standalone binaries, so check the specific server's docs, but npx is the most common entry point.
Local MCPs run as a process on your machine — they start when Claude Code starts, shut down when it closes. Remote MCPs run on someone else's server and Claude connects to them over the network. Remote MCPs are a newer 2026 feature and simpler to share across machines; local MCPs are more private and don't require a constant internet connection.
Only the ones you explicitly give them access to. Filesystem MCP, for example, only reads folders you list in its install command. Most other MCPs (web search, GitHub, etc.) don't touch your local files at all. Still: read the server's source or docs before installing anything that handles sensitive data.
Brave Search. Unambiguously. It's free for casual use, gives an immediate "oh, that's useful" moment, and if you don't like it you can remove it in 10 seconds. Don't try to set up all five at once — add them one at a time as you actually feel the gap they fill.
Two things: (1) Claude Code now supports remote MCP servers without local setup, which is a big deal for sharing configs across machines; (2) the MCP ecosystem is moving toward 50+ curated servers — the signal-to-noise ratio is getting worse, not better. The 5-and-done approach here is more defensible, not less, than it was a year ago.
Most of these MCPs are Claude-specific. MCP is an open protocol, though, and ChatGPT has been adding partial support. For now, assume these 5 are for Claude Code (and Claude.ai's desktop app). The broader ecosystem question is covered in Anthropic's docs as it evolves.
— Leo
Claude Code ships blind — no context gauge, no quota counter. I built a 7-segment statusline and baked in a 50% context handoff rule, backed by Lost-in-the-Middle research. Every segment, every color rule, and the full production script explained.
Intelligence isn't about what you know — it's about how you interact with the world. That one insight explains why AI is growing up in exactly the same order as a human child, and doing it a million times faster.
70 prompt tips for Claude Code are floating around. 7 actually moved the needle for me. Real before/after terminal sessions, a copy-paste cheat sheet, and the 3 patterns I dropped.
The CLAUDE.md I actually use — 67 lines, rewritten three times. Full copy, what I deleted between versions, and the six rules that made the final version stick.
Hands-on AI coding tutorials and workflow deep-dives, straight to your inbox every week.