Repository navigation
best mcp servers
"Best MCP server" is the wrong question in the same way "best library" is. MCP servers give an assistant a capability it did not have, and the capabilities are unrelated: reading your files, querying a database, driving a browser, filing issues. Pick the category first, then judge inside it.
Filesystem and local data. Read and write files on the machine the assistant runs on. The most common first install, and the one with the widest blast radius: an assistant that can write files can write the wrong file.
Code hosting. Issues, pull requests, repository contents. Useful the moment your assistant is doing anything about a codebase it cannot see.
Databases. Schema and queries. The interesting design question here is read-only versus read-write, and the honest default is read-only.
Browsers. Navigate, read and act on live pages. This is the category with the most servers in it and the most differentiation, which is why it has its own page here: choosing an MCP server for browser automation.
Communication. Slack, email, calendars. Reading is usually safe, sending is where you want a confirmation step.
Developer tooling. Debuggers, profilers, log search. Chrome DevTools MCP is the prominent one and it is not a browser-automation server despite driving a browser: Playwright MCP vs Chrome DevTools MCP separates them.
Search and retrieval. Web search, documentation, internal knowledge bases.
Who maintains it. A server written by the vendor of the thing it wraps is usually better maintained than a community wrapper, and community wrappers outnumber official ones. Check the last commit before the star count.
What it can do to you. A server declares tools, and tools act. Read the
tool list before registering: tools/list is a protocol method, so any client
can show you exactly what a server exposes. A server that can delete should be
a deliberate choice.
What it costs in context. Every tool description travels in the model's context on every turn, and so does the JSON schema of its arguments. Measured on our own browser server on 2026-10-12: 17 tools, 3,497 tokens resent on every single turn (9,207 characters of description, counted with a tokenizer). Two servers of that size on a forty-turn session spend about 255,000 tokens restating what the tools are, before a single page has been read.
Whether you will actually use it. The most common mistake is registering five servers because they were interesting. Every one costs context and adds verbs for the model to choose wrongly between.
- Coding assistant, nothing else installed: filesystem plus your code host. Those two cover most of what people mean by wanting MCP.
- The assistant needs to see a live page: one browser server, not two.
- You are debugging your own site's performance: developer tooling, not browser automation.
- You want it to touch production data: read-only first, and add write access only for the specific thing that needed it.
What is the best MCP server? Not a question with an answer. Pick the category you need, then judge maintenance, tool surface and context cost inside it.
How many MCP servers should I register? As few as do the job. Each one costs context on every turn and makes the model's choice harder.
Are official MCP servers better than community ones? Usually better maintained, which is the property that matters over a year. Check the last commit date either way.
Where do I find MCP servers? Directory sites and the protocol's own ecosystem listings exist; the useful filter is maintenance, not count.
Do MCP servers cost money? The servers listed in these categories are generally open source. The model calls they cause are billed by your provider, and an agentic session is turn-heavy.
See also: the MCP server for this project's own, MCP tools, resources and prompts for what a server can actually expose, how many MCP tools is too many for the context arithmetic, and MCP alternatives for when the answer is that you did not need a server at all.
-
The Model Context Protocol documentation, retrieved 2026-09-11, for the protocol operations named above including
tools/list. - This project's own MCP server source, read 2026-09-13, for the tool-count and description-size measurement.
Written while maintaining a browser MCP server, which is one entry in one of the seven categories. It is named in the category where it belongs rather than at the top, and the section arguing for fewer servers argues against registering ours alongside another.
- OpenAI Operator alternatives
- Open-source Operator-style agents
- Is OpenAI Operator still available?
- OpenAI Operator vs Claude computer use
- browser-use alternatives
- Choosing an AI browser agent
- Open-source AI browser agents
- Open-source computer-use agents
- What is an AI web agent?
- AI browser agents vs traditional scraping
- Cloud browser infrastructure for AI agents, explained
- Browserbase alternatives
- Firecrawl vs an AI browser agent
- Skyvern alternatives
- Stagehand vs browser-use
- Project Mariner is gone: what replaced it
- Manus alternatives
- Gemini computer use vs Claude computer use
- A stealth browser MCP, reviewed honestly by its own wiki
- AI browser vs AI browser agent: which one do you want?
- AI browser agent vs RPA: which one fits the job
- AI browser agent vs n8n, Zapier and Make
- Vercel agent-browser alternatives, compared honestly
- What is an agentic browser? Definition and the two kinds
- Open-source agentic browsers: the three layers, compared
- Choosing an MCP server for browser automation: four axes
- Stealth MCP servers compared: Camoufox, nodriver, Patchright
- Playwright MCP alternatives, and the three you don't need
- Autonomous browser agents: the four rungs of autonomy
- What is actually free in the AI browser agent stack
- browser-use on GitHub: what the repo actually gives you
- Playwright MCP vs Chrome DevTools MCP: different jobs
- How to choose among MCP servers: a map by category
- Which MCP servers are worth adding to Claude Code
- MCP on GitHub: finding servers and judging them fast
- MCP vs an API: the decision, and what the wrapper costs
- MCP alternatives: when the protocol is the wrong shape
- Why does my AI agent get blocked?
- The timing signal AI agents give off
- Agent retry loops trip rate limits, not fingerprints
- Claude computer use detected as a bot
- browser-use getting blocked: what you can and cannot change
- Playwright MCP session blocked: four causes, four fixes
- Playwright MCP and captchas: what actually gets you past
- Cloudflare and a browser MCP server: what is being read
- Can an AI agent solve a captcha? The honest answer
- Getting an AI agent to fill out forms
- The best model for an MCP browser agent, and what it really costs
- Browser problem or model problem?
- How to use a Playwright MCP server with Claude Code
- Extracting data to a CSV with an AI agent
- Monitoring a page for changes with an AI agent
- How to let Claude Desktop control a browser
- How to add a browser to Cursor as an MCP server
- Using an AI agent to hunt for apartments
- Getting website data into Google Sheets with an AI agent
- Using an AI agent to download invoices from portals
- AI agents for web research
- Using an AI agent to test your own website
- How to add a browser to Cline as an MCP server
- Posting to social media with an AI agent
- Posting to Facebook with an AI agent
- Posting to Instagram with an AI agent
- Posting to X with an AI agent
- Automating LinkedIn posts: read this first
- Appointment bots: what they are and what an agent can legitimately do
- Track prices across sites with an AI agent
- Build a lead list with an AI browser agent
- Run an AI browser agent on a schedule
- AI browser agent with a local LLM: what changes
- Should you log your AI agent into your accounts?
- How to write a task an AI browser agent can follow
- Move data between two web apps with an AI agent
- The MCP server
- How the tools are shaped, and why
- Playwright MCP vs the Playwright CLI: which fits when
- Playwright MCP: browser is already in use, and the fix
- Playwright MCP best practices: four decisions that matter
- Playwright MCP with a proxy, and the three leaks it leaves
- A browser MCP server in GitHub Copilot: setup and limits
- Using a browser MCP server for web scraping: the pattern
- Which LLM for browser automation: the four properties
- How to build a browser agent, and what to take instead
- Getting an AI agent to log into a website: three routes
- MCP tools, resources and prompts: who controls each
- How many MCP tools is too many? The context arithmetic
- How to build an MCP server: the decisions, not the scaffold
- Local or remote MCP server: what changes, and what does not
- Writing an MCP client in Python: the thirty-line version
- Self-hosted AI agent: what one actually costs to run
- How long an AI browser agent takes per step, measured
- Text, HTML, snapshot or screenshot: what the agent should read
- Giving an AI browser agent a stopping condition
- Keeping an AI browser agent out of destructive actions
- Why did the AI agent click the wrong thing
- When the page changes under the AI agent
- Running one AI agent task across a list of sites
- Seeing a page as it appears in another country
- Getting data out of a dashboard with no export button
- Two browsers in one session: main and support
- Finding the dead links on a site with an AI agent
- Filling a CRM record from a company's website
- One form submission per spreadsheet row, with an AI agent
- Dated screenshots of a page as evidence
- Checking order and delivery status with an AI agent
- Reading a PDF that opens inside the browser
- Summarising a long page or thread with an AI agent
- Collecting every image on a page with its caption
- Collecting event and course listings with an AI agent
- Cancelling a subscription with an AI agent
- What an AI agent can and cannot do inside an iframe
- Shadow DOM and an AI agent: you can click it, you cannot read it
- How to add a browser to Codex as an MCP server
- What a page snapshot costs, per control
- How to let Gemini CLI use a browser
- Native selects and the ones that only look like selects
- Clicking by selector or by coordinates
- How long the agent waits before it gives up
- What a second browser costs
- Uploading a file with an AI agent, and why this one cannot
- Watching the agent work, and when it is worth it
- When not to use an AI browser agent
- Agent or script: deciding once instead of every time
- Using the keyboard instead of the mouse
- Secrets in an agent task: where they end up
- What an agent run should log
- Deduplicating what an AI agent collects
- Normalising values across sites
- Validating an AI agent's output
- Reading a table with an AI agent
- Driving a site's own search and filters
- The task works headed and fails headless
- How to let the AdaL CLI use a browser