Ext Ops Panel
Open dashboard
Comparison

graphql-mcp vs Grafana

graphql-mcp is an MCP server published by parob. Marketplaces we read that list it: 1 (PyPI (MCP servers)). Grafana is an MCP server published by grafana. Marketplaces we read that list it: 4 (Official MCP Registry, Claude Code: claude-plugins-official, Docker MCP Catalog, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacegraphql-mcpGrafana
PyPI (MCP servers) Listed
Version: 3.2.1
Downloads/month (PyPI): 6 695
Downloads/week (PyPI): 3 127
Forks (GitHub): 2
Stars (GitHub): 10
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: v2.2.0
Forks (GitHub): 491
Stars (GitHub): 3 648
Not marked · First seen
Claude Code: claude-plugins-official Not listed Listed
Version: 0.2.0
Forks (GitHub): 5
Stars (GitHub): 19
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:9362bcf6aa0e
Forks (GitHub): 491
Pulls (Docker Hub): 1 164 042
Stars (Docker Hub): 22
Stars (GitHub): 3 648
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 0.2.0
Forks (GitHub): 5
Stars (GitHub): 19
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

graphql-mcp vs Grafana
Factgraphql-mcpGrafana
Marketplaces that list it (differs)1 (worse)4 (better)
Stars (GitHub) (differs)10 (worse)3 648 (better)
Pulls (Docker Hub) (differs)No figure on Docker Hub1 164 042
Forks (GitHub) (differs)2 (worse)491 (better)
Last release (differs)2026-10-29 (worse)2026-11-02 (better)
Where it runs (differs)On your machine (graphql-mcp)Remote server or your machine
Transport (differs)Not statedStreamable HTTP, stdio
Tools it declares (differs)Not published65
Environment variables it asks for (differs)Not published7, secrets among them: 2
Parts of the bundle (differs)Not a bundle2
Licence (differs)MITApache-2.0
Repository (differs)github.com/parob/graphql-mcpgithub.com/grafana/mcp-grafana
Changes in the last 7 days (differs)03
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 14 h ago, requires authentication

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

graphql-mcp

In its own words, on PyPI (MCP servers):

A framework for building Python GraphQL MCP servers.

Grafana

In its own words, on Official MCP Registry:

An MCP server giving access to Grafana dashboards, data and more.

How to run each

graphql-mcp

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Grafana As a remote MCP server

Claude Code
claude mcp add --transport http mcp-grafana https://mcp.grafana.com/mcp

Requires: GRAFANA_PASSWORD (secret), GRAFANA_SERVICE_ACCOUNT_TOKEN (secret), GRAFANA_URL

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Grafana has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of graphql-mcp publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of graphql-mcp publish no settings it asks for, so we do not compare settings.

What it can do: graphql-mcp · What it can do: Grafana · Compare two other plugins

Package data comes from the Python Package Index (pypi.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built