Puppeteer MCP Server vs Sentry MCP

A side-by-side look at pricing, capabilities, pros, cons, and our editorial scores.

	Puppeteer MCP Server MCP Servers	Sentry MCP MCP Servers
Tagline	Reference MCP server that lets LLMs drive a real Chromium browser via Puppeteer.	Official Sentry MCP server: give Claude Code, Cursor, and other AI agents real access to your errors, traces, and triage.
Category	MCP Servers	MCP Servers
Pricing	Free· Free and open source (MIT license). No hosted service; you run it locally under Node/Docker.	Freemium· Free: $0 USD · Team: $4 USD per user/month · Enterprise: $21 USD per user/month
Model	—	Bring-your-own LLM (OpenAI, Anthropic, Azure OpenAI, or OpenRouter) for natural-language search skills; agent-side model is whatever your MCP client runs.
Editorial score	—	—
Use cases	Give Claude a browser to research JS-rendered pagesHave an agent fill and submit a web formTake element-scoped screenshots for bug reportsSmoke-test a local staging site from an LLMScrape specific fields the model identifies visuallyAutomate a signed-in web workflow via headful loginExtract data with in-page JS via puppeteer_evaluatePrototype a custom browser-MCP by forking the reference	Debug production error from IDE agentRoot-cause a latency regression via trace lookupTriage new issues (assign, resolve, comment) from chatCorrelate a failing test with recent Sentry eventsNatural-language search across eventsPost-deploy error-rate investigationPull stack trace and open the offending file for a fixSummarize top issues for a standupQuery self-hosted Sentry from an internal coding agent
Pros	Zero-config bridge between any MCP client and a real Chromium instance, including JS-heavy SPAs that curl or fetch-based tools cannot see. Complete open-source TypeScript reference implementation, easy to fork as a starting point for a hardened production browser-MCP. Ships both NPX (headful, interactive login friendly) and Docker (headless, sandboxed) install paths. Screenshots are exposed as MCP resources with stable names, so a model can refer back to earlier captures across a conversation. puppeteer_evaluate gives the model an escape hatch to run arbitrary in-page JS when the fixed click/fill/select tool set is not enough. Console log resource lets the agent read runtime errors without a separate devtools bridge.	Official first-party server from Sentry — kept in step with API changes, not a community wrapper Both a hosted remote endpoint (mcp.sentry.dev, OAuth or Bearer) and a local stdio binary via npx Works with self-hosted Sentry, not only sentry.io One-line install for Claude Code through the Sentry plugin marketplace; also documented for Cursor and MCP Inspector Fine-grained skill toggles let you scope which tools the agent can call Covers the full debugging loop: issues, events, traces, search, and triage actions like assign/resolve/comment Open source, so the tool surface and prompts can be audited or extended
Cons	Archived on 29 May 2025 (read-only) and no longer maintained by Anthropic; expect Puppeteer/Chromium drift over time. Runs a browser on your machine with access to local files and localhost/private IPs, which is a real prompt-injection and SSRF risk if the model visits hostile pages. No built-in proxy rotation, stealth patches, CAPTCHA handling, or Cloudflare-turnstile bypass, so it is not suitable for anti-bot-hardened targets. Selector-based tools rely on the model producing correct CSS selectors; brittle on frequently-changing DOMs. No session persistence, cookie import, or multi-tab management primitives out of the box. Community forks (Playwright MCP, browserless MCP, hyperbrowser, etc.) have moved past this reference in features and active support.	You still need a paid Sentry plan to get useful volumes of events, retention, and org seats Natural-language search tools require you to bring your own OpenAI/Anthropic/Azure/OpenRouter key — extra cost and setup Value collapses if your team is not already invested in Sentry as its error/APM backend Remote server is single-tenant per token — sharing across a team means each engineer wires their own auth MCP itself is still young; some clients handle remote servers with headers imperfectly and stdio is often the fallback Read/write tools mean a misbehaving agent can resolve or reassign real issues — human-in-the-loop is not optional
Website	github.com	github.com

Pick Puppeteer MCP Server if

✅ Zero-config bridge between any MCP client and a real Chromium instance, including JS-heavy SPAs that curl or fetch-based tools cannot see.
✅ Complete open-source TypeScript reference implementation, easy to fork as a starting point for a hardened production browser-MCP.
✅ Ships both NPX (headful, interactive login friendly) and Docker (headless, sandboxed) install paths.
✅ Screenshots are exposed as MCP resources with stable names, so a model can refer back to earlier captures across a conversation.

Pick Sentry MCP if

✅ Official first-party server from Sentry — kept in step with API changes, not a community wrapper
✅ Both a hosted remote endpoint (mcp.sentry.dev, OAuth or Bearer) and a local stdio binary via npx
✅ Works with self-hosted Sentry, not only sentry.io
✅ One-line install for Claude Code through the Sentry plugin marketplace; also documented for Cursor and MCP Inspector

Compare a different pair →