io.github.mshegolev/prometheus-mcp
prometheus_mcp
Is the io.github.mshegolev/prometheus-mcp MCP server down? No. Installed with mcp<2, it started and listed its tools on 2026-11-01.
Prometheus MCP — query metrics, inspect alerts, and explore scrape targets (read-only).
needs mcp<2 probed 2026-11-14 · unchanged since 2026-11-01
A plain install of the package stops at the import below. These tool definitions are from a second install with mcp<2, started in a container with the network off, on 2026-11-01.
MCP error -32000: Connection closed ModuleNotFoundError: No module named 'mcp.server.fastmcp'. This is mcp 2.x, where FastMCP was renamed to MCPServer (from mcp
- Run it
- uvx --with 'mcp<2' prometheus-mcp@0.1.0 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Reports itself as
- prometheus_mcp 1.30.0
- Capabilities
- experimental, prompts, resources, tools
- Repository
- https://github.com/mshegolev/prometheus-mcp
- Registry
- active, updated 2026-04-18 · registry entry
- Changes
- 2 recorded, reachable in 0 of them. A row is added when the result, the tool count or the cost changes.
Most expensive tools
Estimates with the o200k_base tokenizer.
| Tool | o200k estimate | Share of this server |
|---|---|---|
| prometheus_query_range | 744 | 31 % |
| prometheus_query | 459 | 19 % |
| prometheus_list_targets | 419 | 18 % |
| prometheus_list_metrics | 394 | 17 % |
| prometheus_list_alerts | 346 | 15 % |
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- io.github.mshegolev/gitlab-ci-mcp · needs mcp<2
- io.github.mshegolev/harbor-registry-mcp · needs mcp<2
- io.github.mshegolev/jaeger-mcp · needs mcp<2
- io.github.mshegolev/kibana-mcp · needs mcp<2
- io.github.mshegolev/sonarqube-mcp · needs mcp<2
- ArcGIS MCP Bridge io.github.muend/arcgis-mcp-bridge · needs env
- Cue io.github.murtazox04/cue · alive
- PlayStation Network io.github.murzin-ml/mcp-ps-store · alive
Servers that mention prometheus.
- ai.getvda/kafka-and-postgres-monitoring-stack · newer protocol
- ai.getvda/postgres-kafka-prometheus-stack-generator · newer protocol
- ai.getvda/postgres-prometheus-stack-generator · newer protocol
- io.github.PrometheusAgency/bluesky-brand-monitor · needs auth
- io.github.PrometheusAgency/bluesky-followers-export · needs auth
- io.github.PrometheusAgency/bluesky-scraper · needs auth
- io.github.PrometheusAgency/eu-industrial-emissions · needs auth
- io.github.PrometheusAgency/eudr-parcel-screener · needs auth
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-01 08:14 | needs mcp<2 | 1.3 s | 5 | 3.7k | 2.4k |
| 2026-10-18 06:42 | crashed on start |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The package imports FastMCP from mcp.server.fastmcp. mcp 2.0, the Python SDK of 28 July 2026, renamed FastMCP to MCPServer, and the package asks for mcp with no upper bound, so a plain install (uvx, pip) gets mcp 2.x and the server stops at the import. Installed with mcp<2, it starts and lists its tools. The fix for the publisher: pin mcp<2 in the dependencies, for example mcp>=1.2,<2, and publish a new version, or move to MCPServer as the SDK's migration guide says. Until then, run it with uvx --with 'mcp<2'.
The cause and the fix, with the code before and after: ModuleNotFoundError: No module named 'mcp.server.fastmcp'