Developer tool servers give your agent access to code repositories, browser automation, documentation, and the broader development ecosystem. The best ones handle authentication scoping, rate limits, and multi-client configs as standard.
The official GitHub MCP server. Broad API coverage, fine-grained token scopes, and maintained by the modelcontextprotocol team. The starting point for any code-aware agent.
OpenSpec is the spec-driven development workflow that AI coding agents have been waiting for. The pitch is straightforward: you tell the agent to propose a change (`/opsx:propose add-dark-mode`), and OpenSpec scaffolds a structured artifact bundle: proposal, specs, design, tasks. The agent then applies the tasks one at a time (`/opsx:apply`), and once done, archives the change with the specs updated for the next feature. The 43k stars are the loudest signal in this entire directory and they earn it. The architecture decision worth understanding: OpenSpec is built brownfield-first, scaling from a single developer to enterprise teams while preserving the team's existing workflow. Run it on a Greenfield repo and you get spec-driven development from day one; run it on an existing codebase and the proposals respect what already exists.
Chrome DevTools for Agents gives an AI coding agent the same browser inspection toolkit a human developer uses. It records performance traces and extracts actionable insights, captures screenshots, reads console messages with source-mapped stack traces, and analyses network requests, all driven through Puppeteer for reliable automation. Google ships this as `chrome-devtools-mcp` on npm with full vendor backing from the Chrome DevTools team. The architectural decision worth noting: Google chose to integrate with Chrome DevTools' existing performance API including the Chrome User Experience Report (CrUX) for real-user data, which puts field measurements alongside lab measurements in the agent's hands. The disclosure operators should read carefully: usage statistics are enabled by default, and the README documents how to opt out (`--no-usage-statistics` flag or environment variables). For privacy-sensitive deployments, opting out is one config line.
Codebase awareness layer for accessing repositories, pull requests, issues, code search, and GitHub Actions. Fine-grained PAT scopes keep access minimal.
The leading spec-driven development workflow for AI agents. Implements the /opsx:propose → /opsx:apply → /opsx:archive cycle that scaffolds proposals, specs, design docs, and task checklists, then applies them and archives once shipped.
Vendor-official Chrome DevTools MCP server from the Chrome DevTools team at Google. Lets agents control and inspect a live Chrome browser for automation, debugging, and performance analysis.
Vendor-official Terraform MCP server from HashiCorp. Integrates with the public Terraform Registry (providers, modules, policies) and HCP Terraform / Terraform Enterprise (workspace management, organisation listing, run management, private registry access).
Vendor-built Browserbase MCP server combining cloud browser automation (Browserbase) with natural-language-to-action mapping (Stagehand). 6 tools: start, end, navigate, act, observe, extract. Available as a hosted endpoint at https://mcp.browserbase.com/mcp (LLM costs covered for Gemini) or self-hostable via @browserbasehq/mcp.
AWS Labs server for Infrastructure as Code lifecycle. Validates CloudFormation templates with cfn-lint, checks compliance via cfn-guard against AWS Guard Rules and Control Tower controls, troubleshoots failed deployments with pattern-matched analysis, searches CloudFormation and CDK documentation.
Documentation quality layer that fetches current, version-specific library documentation. Resolves library IDs and returns focused doc sections so your agent works with accurate API references.
Browser interaction layer for navigating pages, clicking elements, filling forms, and taking screenshots. Runs headless Chromium with configurable viewport and user agent.
Community-built Unity Editor MCP bridge. Combines a Unity package (runs inside the editor) with a Node.js MCP server (translates between MCP clients and the editor) to give agents access to scene, GameObject, and component operations.
MCP connects AI agents to external tools. The auth spec is solid. The attack surface around it is wide open. Here is what the protocol enforces, what it leaves to you, and how to close the gaps.
Most agent content focuses on what goes wrong. This article covers what works: the patterns, governance, and practices behind agents that run reliably in production.
The navigation guide to MCP server discovery across 12,000+ servers. Compare PulseMCP, Smithery, Glama, MCP.so, the official registry, and every major index to find the right one for your workflow.
The 10 MCP servers that matter most for automation builders. Hands-on evaluation of each server's capabilities, setup friction, and production readiness.
We score a new dev tools MCP the week it ships. Get the update, plus any re-scores when a server changes enough to move its rating. One email per week maximum.
// Tagged mcp-category-dev-tools · Unsubscribe any time