Essential MCP Servers for Claude Code (and How to Configure Them)

The MCP servers worth installing first — GitHub, Playwright, Context7, Supabase — with the config commands, scopes, and security practices to run them well.

The Model Context Protocol is how Claude reaches beyond its context window: MCP servers give it live access to your repos, browsers, databases, and documentation. With thousands of servers published, the practical question is which handful to configure first — and how to do it without turning your agent into a security liability.

How MCP configuration works

Claude Code manages servers with the claude mcp command family:

# Add a server (stdio transport, runs locally)
claude mcp add <name> <command>

# Add a remote server over HTTP
claude mcp add <name> <url> --transport http

# List and inspect
claude mcp list

Every server has a scope. Local scope (default) applies to you in the current project; project scope writes a .mcp.json file you commit so the whole team shares the config; user scope follows you across projects. Choose deliberately: a database server probably belongs to a project, your personal notes server to your user scope.

The servers worth installing first

Source control

GitHub MCP Server

The official Model Context Protocol server from GitHub. Gives Claude direct access to repositories, issues, pull requests, code scanning, and GitHub Actions through natural language.

The GitHub MCP Server is GitHub's own official MCP implementation, letting Claude read and manage repositories, triage issues, review pull requests, inspect workflow runs, and query code across your account or organization.

It runs remotely (hosted by GitHub with OAuth) or locally via Docker, and granular toolsets let you enable only the capabilities you need — useful for keeping the tool surface small in security-sensitive environments.

Install (Claude Code): claude mcp add github https://api.githubcopilot.com/mcp/ --transport http or run the Docker image locally with a personal access token.

Visit GitHub MCP Server Read more

Browser automation

Playwright MCP

Microsoft's official MCP server that lets Claude drive a real browser using structured accessibility snapshots instead of screenshots — fast, deterministic web automation without vision models.

Playwright MCP exposes browser automation to Claude through Playwright. Instead of pixel-based screenshots, it works from the browser's accessibility tree, which makes interactions fast, lightweight, and deterministic — Claude clicks elements by reference, fills forms, and reads page structure directly.

It's the standard choice for having Claude test web apps, reproduce bugs, scrape JS-rendered pages, or verify UI changes end-to-end.

Install (Claude Code): claude mcp add playwright npx @playwright/mcp@latest

Documentation that isn't stale

Context7

An MCP server that fetches current, version-specific documentation and code examples for thousands of libraries — ending hallucinated APIs from stale training data.

Context7 solves one of the most common failure modes in AI coding: the model confidently using an API that changed two versions ago. Add "use context7" to a prompt (or let Claude call it automatically) and it pulls current, version-specific documentation and real code examples straight into context.

It covers thousands of popular libraries and frameworks and is one of the most-installed MCP servers in the ecosystem.

Install (Claude Code): claude mcp add context7 npx @upstash/context7-mcp

Your database

Supabase MCP Server

The official Supabase MCP server — lets Claude query your database, manage tables, run migrations, and inspect your project configuration through natural language.

The Supabase MCP server connects Claude directly to your Supabase projects: run SQL queries, design and migrate tables, manage database branches, fetch project config, and debug with logs — all from a conversation.

It supports read-only mode and project scoping for safety, which makes it practical to point at real projects rather than throwaway databases.

Install (Claude Code): claude mcp add supabase npx @supabase/mcp-server-supabase with a personal access token.

The reference collection

MCP Reference Servers

The canonical repository of reference Model Context Protocol servers — Filesystem, Fetch, Git, Memory, Time, and more — maintained by the MCP project itself, plus a huge index of community servers.

This is the official reference implementation repository for the Model Context Protocol. It ships maintained servers for core capabilities — Filesystem (secure file operations), Fetch (web content retrieval), Git (repository tools), Memory (persistent knowledge graph), Sequential Thinking, and Time — each demonstrating how MCP servers should be built.

The README doubles as the ecosystem's largest index, linking to hundreds of official integrations and community servers. If you're learning to build your own MCP server or looking for a vetted starting point, start here.

Install (example): claude mcp add memory npx @modelcontextprotocol/server-memory

Security practices that actually matter

MCP servers execute with real credentials, so a few habits pay off:

Scope tokens narrowly. Give the GitHub server a fine-grained token for the repos it needs, not your account-wide PAT. Use read-only modes where servers offer them (Supabase's does).
Prefer official servers. Vendor-maintained servers (GitHub's, Microsoft's, Supabase's) have security teams behind them. For anything else, read the source before wiring it to production data.
Watch your context budget. Every connected server adds tool definitions Claude carries around. Connect the three servers you use daily, not the fifteen you might use someday — you can always add one per-project.
Treat tool output as untrusted. Content fetched by a server (web pages, issue comments) can contain prompt-injection attempts. Claude Code has protections, but least-privilege tokens are what limit the blast radius.

When something doesn't work

Most MCP failures are one of three things: the server process failed to start (run claude mcp list to see status), authentication is missing (check the env vars the server expects), or the transport is wrong (remote servers need --transport http). The /mcp command inside a session shows what's connected and which tools each server exposes.

Going deeper

Browse the full MCPs category for more servers, or see how MCP fits alongside skills, hooks, and plugins in the broader Claude Code configuration stack. If you want to build your own server, the official reference implementations above are the place to start.

Your brand here

Reach our audience of professional directory owners and boost your sales.

Advertise on Claudeable