Seven MCP Servers for Claude Code: Connect Commands and Security Catches
Filesystem, Chrome DevTools, Postgres, Supabase, Stripe, Notion and Exa MCP servers for Claude Code, with connect commands and the access risks of each.
This article is published in English.
Sources: I found 7 MCP servers that make Claude Code feel unfair in 2026
Ask Claude Code why a page is slow and, with the right plug-in, it won't guess from the source. It opens Chrome, records a performance trace, reads the console and reports the actual bottleneck. Most people never see this, because they use it to write code and stop there. What changes the picture is MCP servers: each is a plug that hands the assistant a new capability, such as a browser, a database, a Stripe account or live web search. The official reference repository has passed 90,000 stars, so this isn't a fringe corner of the ecosystem.
Seven servers stand out, some from Anthropic and others from Google, Stripe, Supabase, Notion and Exa. Each entry below says what it lets Claude do, shows the connect command and flags the security catch on anything that can touch real data.
1. Filesystem and Memory: the official starting point
These are Anthropic's own reference servers. Filesystem gives Claude scoped read, write and search access to a folder you explicitly allow, which means the exact path you pass and not the whole machine. Memory is a small persistent knowledge store where Claude can save facts and recall them in a later session, so context stops evaporating between chats. Filesystem is a safe way to let it work across a project's files, and Memory holds project background that would otherwise be re-explained every time.
Neither needs an API key, so they make the simplest introduction to what an MCP server is, with Filesystem doubling as a clear case of limited, scoped access.
Connect Filesystem:
claude mcp add filesystem -- npx -y @modelcontextprotocol/server-filesystem /path/you/allow
Connect Memory:
claude mcp add memory -- npx -y @modelcontextprotocol/server-memory
The catch is that whatever path you give Filesystem is what it can touch. Hand it a narrow folder and never your home directory.
2. Chrome DevTools MCP: debug the live app
From Google, with over 50,000 stars. Claude gets a real Chrome driven through the DevTools protocol, so it can capture performance traces, inspect network requests, collect console errors with proper stack traces and take screenshots. Tell it the dashboard feels slow and to find out why: it profiles the live page and returns the real bottleneck, not a theory. Most bugs live in the running app and not the source, and this server lets the assistant look at that app.
Connect it:
claude mcp add chrome-devtools -- npx -y chrome-devtools-mcp@latest
Chrome and Node must be installed. It also exposes live browser content to the assistant, so keep tabs with sensitive material closed.
3. Postgres MCP Pro: from slow query to suggested index
Plenty of database servers merely run SQL. This one understands the database. It reads query plans, runs health checks on indexes, vacuum and cache, and recommends an index for a slow query using a genuine tuning algorithm and not a hunch. It can even simulate a hypothetical index to test its benefit before you create it. A complaint like this query is slow becomes the plan plus the index that fixes it, backed by the planner's own cost model.
Connect it in the restricted, production-safe form:
claude mcp add postgres-pro -e DATABASE_URI=postgresql://user:pass@host:5432/db -- uvx postgres-mcp --access-mode=restricted
It needs a real connection string, so handle those credentials carefully, and prefer the restricted mode over full read/write unless the database is a throwaway dev instance.
4. Supabase MCP: run the backend from the chat
An official server from Supabase. Claude can query the database, run migrations, read logs and inspect the project without leaving the coding session. For Supabase users that means checking a schema, debugging a problem and running a guarded migration with no detour to the dashboard, so full-stack work happens in one place.
Connect it read-only:
claude mcp add supabase -- npx -y @supabase/mcp-server-supabase@latest --read-only
Keep the read-only flag on. With it the server connects as a read-only database user and turns off every tool that changes data, including migrations, deploys and branch operations. Aim it at a dev project before ever pointing it at production.
5. Stripe MCP: billing in context
Official, from Stripe, and powerful enough that the catch deserves attention. It gives Claude context and actions against Stripe objects such as customers, billing and payments, and helps scaffold integration work grounded in the real account. Billing questions get answered against your actual setup, not generic documentation.
Connect it as a remote server:
claude mcp add stripe --transport http https://mcp.stripe.com
Per Stripe's own documentation, this server can perform write actions, including ones that move money. It's live payment infrastructure. Connect it knowingly, keep it away from anything automated and be sure of the request before making it.
6. Notion MCP: bring the spec into the code
Official, from Notion. Claude can search, read and update Notion pages, databases and comments. A product spec or design doc kept in Notion becomes readable directly while Claude writes code, with no copy-pasting chunks. If a team's documents live there, the context is already written down and this connects it.
One note: Notion now points people to its hosted, OAuth-based MCP and has hinted that the older local server may be retired. Use Notion's official remote OAuth flow, which its docs walk through, and skip the old local token setup.
7. Exa MCP: live search and current library docs
Official, from Exa Labs, around 5,000 stars. Claude gets live web search, with pages returned as tidy markdown, and a second tool that fetches up-to-date code and docs for open-source libraries. Think of it as a relative of Context7: that one concentrates on library docs, while Exa covers wider web search along with code context. Both attack one pain from two sides. When Claude must know what's true on the web today, or what a library's API looks like now, this fetches the answer instead of leaning on training data.
Connect it with a free key:
claude mcp add exa -e EXA_API_KEY=your_key -- npx -y exa-mcp-server
Get a key from the Exa dashboard. A paid service sits behind it, though the free tier is plenty for trying it out.
Don't connect all seven at once
Pick whichever server addresses a frustration from this past week. A sluggish page points to Chrome DevTools, constant re-explaining of a project to Memory, and a painful query to Postgres MCP Pro. Make one of them work on a real task, notice what changes, and only then bring in another. Read the security notes for anything touching real data: Filesystem's scope, Stripe's write access and Supabase's read-only flag. A tool able to act for you earns thirty seconds spent learning what it can reach. MCP isn't a contest to connect the most servers. It's about giving the assistant exactly the hand the job in front of it requires.
Quick answers
What is an MCP server? It's a small program the assistant talks to that adds one ability, whether that's a browser, a database, an API or some other service.
Which first? Filesystem or Memory for seeing how it works without an API key, or Chrome DevTools for an immediate wow on a real app.
Are they safe? The official ones are as trustworthy as the companies behind them. The risk lies in the access you grant, so read the setup notes before connecting anything that can reach files, databases or payments.
Do they cost anything? Mostly no. A couple sit in front of paid services you may already use, like Stripe and Supabase, but connecting the servers is free.