Linear MCP Server vs MCP Fetch Server

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

	Linear MCP Server MCP Servers	MCP Fetch 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)	Official Model Context Protocol reference server that lets any MCP-compatible LLM fetch web pages and read them as clean markdown.
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 tier; you run it locally via uvx, pip, or 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	Reading documentation pages inside Claude DesktopGrabbing a GitHub README before scaffolding a projectSummarising a long article for a chat agentChecking a package changelog during code reviewAnswering questions from a linked spec section by sectionFeeding a URL into an MCP-driven research agentPulling clean markdown for a note-taking workflowVerifying a citation URL inside an editorial pipeline
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	Official reference implementation maintained in the modelcontextprotocol/servers repo — tracks the spec and won't rot behind third-party churn. Zero-install path via `uvx mcp-server-fetch`; Docker image and pip package also available for sandboxed or reproducible setups. HTML-to-markdown conversion produces context-window-friendly output instead of raw tag soup. `max_length` + `start_index` let a model chunk through long pages without blowing its context. Optional Node.js fallback swaps in a more robust HTML simplifier when present. First-class configuration for User-Agent, robots.txt obedience, and outbound proxy — practical knobs for real-world scraping etiquette. Works out of the box with every major MCP client (Claude Desktop, Claude Code, VS Code, Cursor, Zed, Continue).
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	No JavaScript rendering — SPAs, Cloudflare-challenged pages, and content loaded after DOMContentLoaded come back empty or as a shell. No built-in anti-bot handling; sites that block plain HTTP clients (many news sites, LinkedIn, X) will 403. Security caveat called out in the README: the server can reach local/internal IPs, so it is a genuine SSRF risk if exposed to an untrusted model or user. Single tool, single verb — for crawling, sitemap walks, or extracting structured data you need a heavier server like Firecrawl-MCP or a Playwright-based one. Truncation defaults to 5,000 characters; models that don't understand `start_index` can silently miss content below the fold.
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 MCP Fetch Server if

✅ Official reference implementation maintained in the modelcontextprotocol/servers repo — tracks the spec and won't rot behind third-party churn.
✅ Zero-install path via `uvx mcp-server-fetch`; Docker image and pip package also available for sandboxed or reproducible setups.
✅ HTML-to-markdown conversion produces context-window-friendly output instead of raw tag soup.
✅ `max_length` + `start_index` let a model chunk through long pages without blowing its context.

Compare a different pair →