Linear MCP Server vs Puppeteer MCP Server

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

	Linear MCP Server MCP Servers	Puppeteer MCP Server MCP Servers
Tagline	Open-source MCP server bridging LLM agents to Linear's issue tracker (now deprecated in favour of Linear's official remote MCP)	Reference MCP server that lets LLMs drive a real Chromium browser via Puppeteer.
Category	MCP Servers	MCP Servers
Pricing	Free· Free and open source (MIT). Requires a Linear account and personal API key; Linear itself is free for small teams, $8/user/mo Standard, $14/user/mo Plus.	Free· Free and open source (MIT license). No hosted service; you run it locally under Node/Docker.
Model	—	—
Editorial score	—	—
Use cases	Filing bugs from Claude Desktop or Cursor without leaving the editorAgent-driven triage of the inbox projectBulk relabeling or reprioritising issues via natural languageStandup summaries of a user's assigned Linear workAdding comments to tickets from a coding agent's PR reviewReference implementation for building a custom Linear MCP server	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
Pros	Open source (MIT) and small enough to read end-to-end in an afternoon One-line install via Smithery or straight npx in Claude Desktop config Covers the create / update / search / comment loop that 90% of ticket workflows need Works with any MCP client, not just Claude Desktop (Cursor, Zed, Continue, custom agents) Clear tool schemas make it a good reference implementation for building your own MCP servers Uses Linear's official GraphQL API, so permissions and audit trails stay intact	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.
Cons	Officially deprecated by its author in favour of Linear's own remote MCP server at mcp.linear.app/sse Runs as a local stdio process, so it has to be installed on every workstation and cannot be shared across a team Uses a personal API key, meaning every action shows up as the key owner rather than the actual LLM user Tool coverage is narrower than the official server: no cycles, projects, roadmaps, or workflow state management Error handling and rate-limit backoff are minimal; heavy agent loops can trip Linear's API limits	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.
Website	github.com	github.com

Pick Linear MCP Server if

✅ Open source (MIT) and small enough to read end-to-end in an afternoon
✅ One-line install via Smithery or straight npx in Claude Desktop config
✅ Covers the create / update / search / comment loop that 90% of ticket workflows need
✅ Works with any MCP client, not just Claude Desktop (Cursor, Zed, Continue, custom agents)

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.

Compare a different pair →