// blog

MCP Servers for AI Agents: Which Ones Are Worth Installing in 2026

May 23, 2026

MCP Servers for AI Agents: Which Ones Are Worth Installing in 2026

If you are building anything with AI agents this year, you have probably bumped into MCP servers by now. The Model Context Protocol went from a curious spec to something your agents actually depend on, and the server ecosystem has exploded. Last count there were hundreds of MCP servers floating around GitHub, npm, and PyPI. Most of them are half-finished weekend projects.

I pulled review data from the Gearscope catalog to figure out which MCP servers are worth installing. Every pick below was tested hands-on or in a sandbox, rated across quality, documentation, setup, value, and ecosystem fit. No hand-waving.

Here are six MCP servers that earned their spot.


1. Engram

Rating: 5/5 | Verdict: KEEP IT Author: Gentleman Programming (Alan Buscaglia) License: MIT

GitHub

Engram is a persistent memory system for AI coding agents. It ships as a single Go binary backed by SQLite with full-text search, and it exposes four interfaces: MCP server (stdio transport), HTTP API, CLI, and an interactive TUI.

When your agent finishes a session, Engram captures what happened and stores it so the next session can pick up where things left off. That sounds simple, but it solves one of the most annoying problems with agent workflows: context amnesia between runs.

Strengths:

  • Single binary, zero config drama. Download and run.
  • Perfect 5/5 scores across every review dimension: quality, docs, setup, value, ecosystem fit.
  • SQLite with FTS5 means search is fast and reliable.
  • Four interfaces mean you can use it however you want.

Weaknesses:

  • Partial functional verification in testing. The core works, but edge cases around concurrent access patterns need more real-world stress testing.
  • Stdio-only MCP transport. If you need SSE transport for a remote setup, you will need to wrap it yourself.

If you run agents locally and are tired of them forgetting everything, Engram is the first thing to install.


2. Laravel Boost

Rating: 5/5 | Verdict: KEEP IT Author: Laravel (Taylor Otwell) License: MIT

GitHub

Laravel Boost is the official Laravel MCP server. It lives inside your Laravel application and gives agents direct access to your database schema, query logs, application info, and documentation search. It ships 10 MCP tools and 4 prompts, with auto-config for 11 different AI agents.

This is what vendor-backed MCP tooling should look like. Instead of a generic code assistant guessing at your Eloquent models, Boost hands the agent your actual schema, your actual routes, and your actual error logs.

Strengths:

  • Dead simple setup. Composer install, one command, done. 5/5 setup score.
  • 5/5 quality, value, and ecosystem fit. It does exactly what it promises.
  • Auto-config means it works with Claude Code, Codex, Cursor, and eight more agents out of the box.
  • Real production tooling from the Laravel team, not a community prototype.

Weaknesses:

  • Laravel only. If you are on Django, Rails, or anything else, this does nothing for you.
  • Documentation is good but not exhaustive at 4/5. Some advanced tool configurations could use more examples.
  • Partially verified. The database tools work well, but some edge cases with complex Eloquent relationships were not fully tested.

If you build with Laravel, stop reading and go install this. It is not optional anymore.


3. bb-browser

Rating: 4/5 | Verdict: TRY IT Author: epiral License: MIT

GitHub

bb-browser is an MCP server and CLI that connects AI agents to your actual Chrome browser via the Chrome DevTools Protocol. Instead of spinning up headless browsers or fighting anti-bot captchas, it runs JavaScript inside browser tabs where you are already logged in. It ships 143 community platform presets.

The idea is straightforward: your browser becomes the API. No API keys, no headless Chrome, no anti-bot detection. Your agent just uses your existing session.

Strengths:

  • 5/5 value. Using your real login session removes an entire class of integration headaches.
  • 143 platform presets means it already knows how to interact with most sites you care about.
  • No API keys to manage. Your cookies and sessions are the auth.

Weaknesses:

  • Setup is 3/5. Chrome DevTools Protocol configuration is not always smooth, especially if you run multiple Chrome profiles or have strict security settings.
  • Partial verification. The 143 presets sound great, but many were not individually tested.
  • Security model requires thought. You are giving an agent access to your logged-in browser. That is powerful and also dangerous. Know what you are doing.

bb-browser is worth trying if you need agents to interact with web apps that do not have APIs. Just be deliberate about which browser profile you point it at.


4. Agent Toolkit for AWS

Rating: 4/5 | Verdict: KEEP IT Author: Amazon Web Services License: Apache-2.0

GitHub

Amazon's official agent toolkit ships 43 skills (13 core, 30 specialized) covering CDK, CloudFormation, Bedrock, EC2, VPC networking, and data analytics. It also includes a managed MCP server that works with Claude Code, Codex, and Kiro.

This is the real deal for AWS shops. The depth of reference material outclasses every third-party AWS skill pack I have seen.

Strengths:

  • 5/5 documentation. AWS clearly invested in making the reference material thorough and accurate.
  • 5/5 ecosystem fit. If your infrastructure runs on AWS, this fits perfectly.
  • 43 skills covering everything from infrastructure-as-code to data analytics. That is genuine breadth with real depth.
  • Managed MCP server means no manual server process to babysit.

Weaknesses:

  • Setup is 4/5, not because it is hard, but because you need valid AWS credentials configured before anything works. That is not the tool's fault, but it is a gate.
  • AWS-only. If you are on GCP or Azure, this is not for you.
  • Partial verification. The breadth is huge, and not every skill was tested end-to-end.

If AWS is your cloud, this toolkit is a no-brainer install. The documentation alone is worth it.


5. Snyk Agent Scan

Rating: 4/5 | Verdict: KEEP IT Author: Snyk (formerly Invariant Labs) License: Apache-2.0

GitHub

Snyk Agent Scan is not an MCP server that gives your agent new capabilities. It is a security scanner built for the agent ecosystem. It crawls your machine for MCP server definitions, SKILL.md files, and tool descriptions, then checks everything against a catalog of 15+ issue types: prompt injection, tool poisoning, supply-chain threats, and more.

This is the kind of tool you did not know you needed until you realize you are installing random MCP servers from GitHub without auditing them first.

Strengths:

  • 5/5 setup. Install, run, get results. As simple as security tooling gets.
  • 5/5 ecosystem fit. As MCP server adoption grows, the attack surface grows with it. This tool addresses a real and growing problem.
  • Actually connects to your MCP servers, retrieves their tool manifests, and inspects what they expose. Not just static analysis.

Weaknesses:

  • Quality and documentation both sit at 4/5. Good but not exceptional. Some issue types could use clearer explanations in the output.
  • Partial verification. New issue types are being added regularly, so coverage is a moving target.
  • It tells you what is wrong but does not fix anything. You still need to understand the findings and act on them.

Install Snyk Agent Scan alongside whatever MCP servers you pick up. Think of it as the antivirus for your agent stack. You would not install npm packages without auditing them, and you should not install MCP servers without scanning them either.


6. Browserbase Skills

Rating: 4/5 | Verdict: KEEP IT Author: Browserbase License: MIT

GitHub

Browserbase Skills is the official skill pack from Browserbase, a cloud browser infrastructure provider. It contains 13 skills for browser automation, web scraping, serverless browser functions, UI testing, trace capture, cookie sync, and company research.

Think of this as the production-grade sibling to bb-browser. Where bb-browser uses your local Chrome session, Browserbase gives you cloud browsers that scale.

Strengths:

  • 5/5 documentation and 5/5 value. The skills are well-written and cover real workflows.
  • 5/5 ecosystem fit. Works with Claude Code, Codex, Cursor, and the rest.
  • Covers the full browser automation pipeline from basic fetch to adversarial UI testing.

Weaknesses:

  • Requires a Browserbase account and API key. This is a cloud service, not a self-hosted tool.
  • 4/5 quality. Some skills are tighter than others. The breadth is good but depth varies.
  • Partial verification. Complex multi-step browser workflows were not all tested exhaustively.

If you need production browser automation at scale, this is the better pick over bb-browser. If you just need quick local browser control and want zero cloud dependency, go with bb-browser instead.


Quick Comparison

Server Rating Best For Setup Cost
Engram 5/5 Persistent agent memory Dead simple Free, self-hosted
Laravel Boost 5/5 Laravel project context Dead simple Free, self-hosted
bb-browser 4/5 Local browser control Moderate Free, self-hosted
AWS Agent Toolkit 4/5 AWS infrastructure Moderate Free, needs AWS creds
Snyk Agent Scan 4/5 Security auditing Dead simple Free, open source
Browserbase Skills 4/5 Cloud browser automation Easy Needs Browserbase account

What I Actually Run

If you want the short version: Engram and Snyk Agent Scan go on every machine I use agents on, regardless of project. Laravel Boost is automatic for any Laravel work. The AWS toolkit goes on when I am touching infrastructure. bb-browser and Browserbase are situational picks depending on whether I need browser automation locally or in the cloud.

The MCP server space is moving fast. New servers show up weekly, and the quality range is wild. The six above are the ones that held up under actual testing. Install what fits your stack, skip what does not, and always scan before you trust.