Sentry
SentryOfficial
Search errors and traces, triage issues and debug failures in Sentry from a coding assistant.
- Category
- Developer Tools
- Connection
- Remote · Local
by Google
Let a coding agent drive a live Chrome browser to debug pages, inspect network traffic and record performance traces.
Best for
Coding agents that should check their own front-end changes in a real Chrome: reading console errors, watching network calls and measuring performance after an edit.
This server runs on your machine. Pick your client for the matching config; placeholders stand in for any secrets.
Before you connect
The server exposes the content of the browser instance to the MCP client, which can inspect, debug and modify any data in the browser or DevTools. The README advises against sharing sensitive or personal information you don't want the client to see.
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": [
"-y",
"chrome-devtools-mcp"
]
}
}
}Format checked Oct 30, 2026 against Claude Desktop documentation. Client settings change, so confirm with the client's own docs.
npm package · stdiochrome-devtools-mcp@1.12.0
Chrome DevTools MCP gives a coding assistant the inspection tools a developer would reach for in the browser. It can open a page, read console messages with source-mapped stack traces, look at network requests, take screenshots and record performance traces, then act on the page through Puppeteer-based automation. It runs on your machine through npx and starts Chrome only when a tool needs a browser. The README says performance tools may send trace URLs to the Google CrUX API for field data, and that usage statistics are collected unless you opt out with a flag.
No account or API key is mentioned. It needs a current Node.js LTS release, npm and the current stable Chrome. The README says only Google Chrome and Chrome for Testing are officially supported.
npm package
Statements on this page come from
Registry name io.github.ChromeDevTools/chrome-devtools-mcp. The registry only lets an organization's owners publish under its io.github.<org> namespace (registry authentication docs, read 2026-10-30). The repository is in the ChromeDevTools organization, which also holds the DevTools frontend the README links to, and the README says Google collects usage statistics for Chrome DevTools MCP under the Google Privacy Policy (read 2026-10-31).
Listing on HistChat is not an endorsement or a security review. MCP servers can access data or perform actions, so review the source and permissions before connecting.
SentryOfficial
Search errors and traces, triage issues and debug failures in Sentry from a coding assistant.
GitHubOfficial
Let an assistant browse repositories, triage issues, handle pull requests and check Actions runs on GitHub.
Grafana LabsOfficial
Search dashboards, query Prometheus and Loki, and work with incidents in a Grafana instance from an assistant.
GitLabOfficial
Connect an assistant to GitLab projects, issues and merge requests through the MCP endpoint built into GitLab itself.
Model Context ProtocolReference
Let an assistant read, search and edit files in the folders you choose on your own machine.
MicrosoftOfficial
Give an assistant control of a real browser to navigate pages, click, type and read page structure.