Moxie Docs
All guides

MCP servers

The best MCP servers for coding

MCP servers let your coding agent reach past its training data — into your files, your tools, your errors, and current documentation. Here are eleven worth knowing, what each does, and who actually maintains it.

Last reviewed: June 2026

How to read this list

The Model Context Protocol has a reference set of servers maintained by its steering group, but those are demonstrations, not production tools. Many once-popular reference servers — GitHub, GitLab, Slack, Google Drive — have been archived and handed off to the actual vendors. So when we say “official” below, we mean maintained by the vendor whose system it connects to, not simply listed in the reference repo.

One caution worth repeating: connecting more than a handful of servers floods your agent with tools and tends to hurt its performance. Start with two or three that fit your workflow, and add more only when you feel the gap.

The list

Eleven MCP servers worth knowing

  1. 1. GitHub MCP Server

    Official · GitHub

    Search code, read and manage issues and pull requests, and automate repo workflows. The hosted remote server (OAuth) is the recommended path and adds tools the local version lacks. It's distinct from the original, now-archived reference GitHub server.

  2. 2. Filesystem

    Reference · MCP steering group

    Secure, access-controlled local file operations. One of the most widely installed servers because it ships in most starter kits.

  3. 3. Git

    Reference · MCP steering group

    Read and manipulate a local Git repository — distinct from the GitHub API server above.

  4. 4. Sequential Thinking

    Reference · MCP steering group

    Structured, multi-step reasoning that lets an agent work a hard problem through an explicit chain of thoughts.

  5. 5. Fetch

    Reference · MCP steering group

    Fetches a URL and converts the page to clean Markdown the model can actually read.

  6. 6. Context7

    Vendor · Upstash (MIT)

    Injects up-to-date, version-specific docs and code examples for public libraries into your prompt, so the agent writes against the current API instead of stale training data.

  7. 7. Playwright MCP

    Official · Microsoft

    Browser automation driven by the page's accessibility tree rather than screenshots — for agents that need to click through and test a real web app.

  8. 8. Sentry MCP

    Official · Sentry

    Pulls production errors, issues, and events into the agent for debugging, with an optional AI root-cause step. Available as a hosted remote server.

  9. 9. Supabase MCP

    Official · Supabase

    Manage Supabase projects, run SQL, and work with auth, storage, and edge functions from the agent. OAuth by default.

  10. 10. Chrome DevTools MCP

    Official · Google

    Control and inspect a live Chrome instance — performance, DOM, and network — a Google-maintained option for front-end debugging.

  11. 11. Moxie Docs MCP

    Vendor · Moxie Docs

    Serves living documentation for your own codebase: conventions, doc gaps, references, and verified commands, scoped per repository and read-only. Where Context7 brings in public library docs, Moxie brings in accurate context about your private code — and keeps it current as the code changes.

“Official” means maintained by the vendor whose system the server connects to. Reference servers are demonstrations from the MCP steering group. Several older reference servers (GitHub, GitLab, Slack, Google Drive, Brave Search) have been archived in favor of vendor-maintained replacements. Details reflect each project's public documentation at the time of writing.

Start small

Pick the two or three servers that match how you actually work — a file or Git server, something for current docs, and one for whatever system you debug most. Add Moxie Docs when you want your agent to follow your codebase's own conventions instead of rediscovering them every prompt.

See the Moxie Docs MCP serverCompare plans

FAQ

Frequently asked questions

Quick answers to the questions developers ask about Best MCP servers for coding.

What is the best MCP server for coding?+

There's no single best one — it depends on your workflow. A file or Git server plus a documentation-context server like Context7 or Moxie Docs covers most coding needs. Add a browser server (Playwright) or error-tracking server (Sentry) if your work calls for it.

Are the official MCP servers free?+

The reference servers are open-source and free. Vendor-maintained servers are usually free to run but may require an account or paid plan for the underlying service — for example, a Sentry or Supabase project.

How many MCP servers should I connect?+

Start with two or three. Connecting many servers at once gives the agent too many tools to choose from and tends to degrade its performance. Add more only when you hit a real gap.

What's the difference between Context7 and Moxie Docs?+

Context7 injects up-to-date documentation for public libraries into your agent. Moxie Docs generates and maintains documentation for your own private codebase and serves it over MCP. They solve different halves of the context problem and are often used together.

Keep reading

Related guides

Get started

Give your agents real codebase context.

Connect a repository and Moxie Docs generates living documentation and serves it to your agents over MCP. 14-day free trial, no charge today.

Connect GitHubView pricing