Grafana MCP vs MCP Everything Server

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

	Grafana MCP MCP Servers	MCP Everything Server MCP Servers
Tagline	Official Grafana Labs MCP server — dashboards, Prometheus, Loki, alerts and incidents in your LLM client	The kitchen-sink reference MCP server that exercises every corner of the Model Context Protocol
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 License). No cloud service or paid tier — you run it locally via npx, Docker, or your MCP client of choice.
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	MCP client conformance testingRegression testing of stdio and Streamable HTTP transportsVerifying sampling round-trip behavior in a new agent hostDebugging elicitation UI in an IDE integrationReference reading for authoring a new MCP serverDemoing MCP primitives in workshops and talksSmoke-testing cancellation and progress-notification handlingValidating resource-subscription update delivery
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	Only server that exercises the full MCP feature matrix in one place — tools, resources, prompts, sampling, elicitation, roots, logging, subscriptions, and Tasks Maintained by the Model Context Protocol project itself, so behavior tracks the spec as it evolves (SEP-1686 Tasks, Streamable HTTP, etc.) Runs anywhere an MCP client runs — npx, Docker, Claude Desktop, VS Code, Cursor, Windsurf — with stdio or HTTP transports TypeScript source is short and readable, making it a de-facto reference for how each handler should be shaped MIT-licensed, no telemetry, no signup, no cloud dependency Includes progress notifications and cancellation flows that most tutorial servers skip, so client cancel/timeout logic can be exercised properly
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	Explicitly not useful for end users — it does not do anything a human would actually want done Feature drift means some primitives (SEP-1686 Tasks, elicitation) may not yet be implemented in every client, producing red herrings during testing Documentation is a single features.md; there is no guided tour that maps each tool to the spec section it exercises TypeScript-only reference — Python or Rust client authors have to translate patterns themselves Sampling and elicitation flows depend on the client honoring them, so a silent client makes it hard to tell whether the server or the client is at fault
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 MCP Everything Server if

✅ Only server that exercises the full MCP feature matrix in one place — tools, resources, prompts, sampling, elicitation, roots, logging, subscriptions, and Tasks
✅ Maintained by the Model Context Protocol project itself, so behavior tracks the spec as it evolves (SEP-1686 Tasks, Streamable HTTP, etc.)
✅ Runs anywhere an MCP client runs — npx, Docker, Claude Desktop, VS Code, Cursor, Windsurf — with stdio or HTTP transports
✅ TypeScript source is short and readable, making it a de-facto reference for how each handler should be shaped

Compare a different pair →