Skip to main content
📖 The AI Tool Bible

Cloudflare MCP Server vs Linear MCP Server

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

 Cloudflare MCP Server logo
Cloudflare MCP Server
MCP Servers
Linear MCP Server logo
Linear MCP Server
MCP Servers
TaglineOfficial suite of remote MCP servers that let Claude, Cursor, and other agents read and control your Cloudflare account.Open-source MCP server bridging LLM agents to Linear's issue tracker (now deprecated in favour of Linear's official remote MCP)
CategoryMCP ServersMCP Servers
PricingFreemium· Free: $0 USD · Team: $4 USD per user/month · Enterprise: $21 USD per user/monthFree· 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.
Model
Editorial score
Use cases
Debugging Workers with live logs from chatDeploying and configuring Workers bindingsGrounded Q&A over Cloudflare developer docsQuerying Radar for real-time internet traffic dataPulling audit logs for compliance answersRunning a headless browser via Browser RenderingAutoRAG pipelines against R2-hosted corporaReviewing Cloudflare One CASB findingsDNS analytics and Logpush inspectionBuilding custom MCP servers from the Demo Day template
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
Pros
  • Official, first-party servers maintained by Cloudflare with 4k+ GitHub stars and active development.
  • Remote-hosted at stable URLs so most clients need only a URL and OAuth login, no local install.
  • Split into 16 focused servers so agents get relevant tools without prompt bloat.
  • Covers most of the Cloudflare platform: Workers, R2, KV, D1, Radar, DNS analytics, AI Gateway, AutoRAG, Browser Rendering, audit logs, CASB.
  • Works with any MCP-capable client - Claude Desktop, Claude Code, Cursor, Windsurf, and OpenAI Responses API.
  • Apache 2.0 source is on GitHub, so teams can self-host, audit, or extend any server.
  • Docs AI Search server gives agents grounded answers over the full developers.cloudflare.com corpus.
  • 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
Cons
  • Only useful if you already run on Cloudflare - it is not a general cloud MCP.
  • Advanced capabilities inherit Cloudflare paywalls (Browser Rendering, AutoRAG, CASB, Cloudflare One all require paid plans).
  • Write-capable tools mean a compromised or over-permissioned token can push destructive changes; scoping API tokens carefully is on you.
  • Because the servers are hosted by Cloudflare, your agent's queries and returned data traverse Cloudflare infrastructure - not ideal for teams that want everything to stay in-VPC.
  • OAuth and remote-MCP support is still uneven across MCP clients, so setup varies and some clients need a manual token instead.
  • Sixteen separate endpoints can be confusing - discovery of which server owns which capability is not always obvious from client-side.
  • 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
Websitegithub.comgithub.com
Pick Cloudflare MCP Server if
  • Official, first-party servers maintained by Cloudflare with 4k+ GitHub stars and active development.
  • Remote-hosted at stable URLs so most clients need only a URL and OAuth login, no local install.
  • Split into 16 focused servers so agents get relevant tools without prompt bloat.
  • Covers most of the Cloudflare platform: Workers, R2, KV, D1, Radar, DNS analytics, AI Gateway, AutoRAG, Browser Rendering, audit logs, CASB.
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)