kapyn
All postsServer racks in a data center with blue lighting
Guide

Best MCP servers for Claude in 2026

MCP turns Claude from a chatbot into an agent that can read your files, query your database, and call your APIs. Here are the servers worth wiring up.

The best MCP servers to install in 2026 are: Filesystem (read and write local files), Fetch (make HTTP requests), Supabase MCP (query your database), Playwright MCP (control a browser), and GitHub MCP (manage repos and PRs from the conversation). These five cover 90% of real agentic workflows. Everything else is additive.

Model Context Protocol (MCP) is the open standard that lets AI models communicate with external tools. Instead of copy-pasting data into a chat window, an MCP server exposes tools the model can call natively — read a file, run a query, submit a form — and get structured results back. The practical effect: Claude can operate your development environment, not just advise on it.

Setup: where does MCP config live?

MCP servers are configured in ~/Library/Application Support/Claude/claude_desktop_config.json on Mac (or the equivalent path on Windows/Linux). Most servers run via npx with no separate install step — just add the config and restart Claude Desktop.

The core three: Filesystem, Fetch, and Memory

The Filesystem server is non-negotiable for any coding or file-management workflow. It gives Claude read and write access to specified directories — meaning it can read a config file, edit a component, and create a new file in one conversation turn. The security model lets you restrict access to specific paths, so you don't need to give it access to your whole machine.

The Fetch server lets Claude make HTTP requests and parse the responses. This turns it into a capable API tester, web researcher, and scraper. "Check the status of this endpoint" or "fetch the docs for this library and summarize the auth section" go from multi-step copy-paste exercises to single instructions.

The Memory server maintains a persistent knowledge graph across conversations. By default, Claude forgets everything between sessions. With Memory, it can store facts, preferences, and working knowledge that carry forward — making it far more useful as a long-running assistant on a project.

json
{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/Users/you/projects"]
    },
    "fetch": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-fetch"]
    },
    "memory": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-memory"]
    }
  }
}

For developers: GitHub and Supabase

The GitHub MCP server exposes the GitHub API as tools Claude can call directly: create a branch, open a PR, read issue comments, push a commit. This is the bridge between an AI that can write code and one that can actually participate in a development workflow. It's particularly powerful combined with Claude Code — describe a feature, have it implement and commit, then open the PR from the same conversation.

The Supabase MCP server connects Claude to your Supabase database. It can read and write rows, run SQL queries, and introspect the schema. The most useful pattern: describe a data migration in plain English, have Claude write and validate the SQL, then execute it — all inside the conversation, with the SQL visible for review before it runs.

Playwright MCP gives Claude control of a real browser — it can navigate to URLs, click elements, fill forms, and extract page content. This is qualitatively different from the Fetch server, which only retrieves raw HTML. Playwright handles JavaScript-rendered pages, can log into services, and can automate multi-step web workflows. The obvious power tool for QA automation and web scraping.

Brave Search MCP connects Claude to Brave's search API (requires a free API key). Useful for any research workflow where the model needs current information beyond its training cutoff — competitive analysis, recent product releases, latest documentation.


Start with Filesystem and Fetch. Add GitHub or Supabase once your codebase is involved. Add Playwright when you need real browser automation. The full MCP catalog — with hundreds of community servers for Slack, Linear, Notion, AWS, and more — lives on the Radar.

Find these on the Radar

Every tool here lives on Kapyn Radar. Save the ones that fit into a Loadout and find them again.

Open the Radar

Keep reading