Grafana MCP vs Linear MCP Server

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

	Grafana MCP MCP Servers	Linear MCP Server MCP Servers
Tagline	Official Grafana Labs MCP server — dashboards, Prometheus, Loki, alerts and incidents in your LLM client	Open-source MCP server bridging LLM agents to Linear's issue tracker (now deprecated in favour of Linear's official remote MCP)
Category	MCP Servers	MCP Servers
Pricing	Free· Free and open source (Apache 2.0). You still need a Grafana instance — OSS Grafana is free; Grafana Cloud has a free tier plus paid Pro/Advanced/Enterprise plans.	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.
Model	—	—
Editorial score	—	—
Use cases	Incident investigation from Claude DesktopConversational PromQL and LogQL queryingDashboard search and summarisationPanel screenshot analysis by vision LLMsAlert rule and notification policy reviewOn-call schedule lookupsSift automated error-pattern triageCursor / VS Code observability copilotMulti-tenant SSE server for internal agentsGrafana Incident timeline updates from an agent	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 Grafana Labs project, actively developed with 3k+ GitHub stars and Apache-2.0 licensing Broad coverage: dashboards, alerts, incidents, on-call, Sift, annotations, snapshots, plus native query support for Prometheus, Loki, and eight SQL/timeseries backends Panel PNG rendering lets vision-capable LLMs actually see charts, not just JSON Three transports (stdio, SSE, Streamable HTTP) cover single-user desktop and multi-client server deployments Per-tool enable list and --disable-write flag make it safe to hand to autonomous agents against production Grafana Works out of the box with Claude Desktop, Cursor, VS Code and any MCP-spec client via uvx or Docker	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	Requires Grafana 9.0+ and a service account token — no value without an existing Grafana deployment Many powerful tools are disabled by default and must be explicitly enabled, which is safer but adds config friction Broad tool surface can flood a model's context window; you often need to curate which tools are exposed per assistant PromQL/LogQL/SQL responses are raw datasource output — the LLM still has to reason about large result sets, which burns tokens fast Not a hosted service: you run and secure the process yourself, and network reachability to Grafana is your problem	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
Website	github.com	github.com

Pick Grafana MCP if

✅ Official Grafana Labs project, actively developed with 3k+ GitHub stars and Apache-2.0 licensing
✅ Broad coverage: dashboards, alerts, incidents, on-call, Sift, annotations, snapshots, plus native query support for Prometheus, Loki, and eight SQL/timeseries backends
✅ Panel PNG rendering lets vision-capable LLMs actually see charts, not just JSON
✅ Three transports (stdio, SSE, Streamable HTTP) cover single-user desktop and multi-client server deployments

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)

Compare a different pair →