Chrome DevTools MCP
Let coding agents inspect, debug and profile a live Chrome browser.
How it runs
This server runs on your own machine. Your MCP client starts it as a local process (usually through npx, uvx or Docker) and talks to it over standard input/output. It runs with your user's permissions, so scope paths and credentials tightly.
Who maintains it
This is an official server published by the vendor behind the product it connects to, generally the safest choice for that integration.
Safety checklist
- Review which tools it exposes, and prefer read-only modes where available.
- Use scoped, least-privilege credentials or a test account first.
- Keep human approval on for actions with side effects (writes, payments, deletions).
- Treat content returned from the web or user data as untrusted, because it can contain prompt-injection attempts.
Similar MCP servers
GitHub MCP Server
GitHub's official server for repositories, issues, pull requests and Actions.
Context7
Up-to-date, version-specific library documentation and code examples for coding agents.
Microsoft Learn MCP
Search and fetch official Microsoft documentation.
Sentry MCP
Investigate Sentry issues, errors and releases from your agent.
Semgrep MCP
Scan code for security vulnerabilities with Semgrep.
Grafana MCP
Search dashboards, query data sources and manage incidents in Grafana.