Ext Ops Panel
Open dashboard
Comparison

Prometheus MCP Server vs Mimir — Persistent Memory Engine

Mimir — Persistent Memory Engine is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑20.

Prometheus MCP Server is an MCP server published by pab1it0. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). Mimir — Persistent Memory Engine is an MCP server published by tcconnally. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-29. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplacePrometheus MCP ServerMimir — Persistent Memory Engine
Official MCP Registry Listed
Version: 1.6.2
Forks (GitHub): 105
Stars (GitHub): 521
Not marked · First seen
Removed on 2026-10-20
Version: 2.0.0
No figure published
Not marked · First seen
Docker MCP Catalog Listed
Version: sha256:3c3921301229
Forks (GitHub): 105
Stars (GitHub): 521
Not marked · First seen
Not listed

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

Prometheus MCP Server vs Mimir — Persistent Memory Engine
FactPrometheus MCP ServerMimir — Persistent Memory Engineno longer listed ·
Marketplaces that list it (differs)20
Stars (GitHub) (differs)521No figure on GitHub
Forks (GitHub) (differs)105No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (ghcr.io/pab1it0/prometheus-mcp-server:1.6.2)Not stated
Transport (differs)stdioNot stated
Tools it declares (differs)6Not published
Environment variables it asks for (differs)14, secrets among them: 2Not published
Licence (differs)MITNot stated
Repository (differs)github.com/pab1it0/prometheus-mcp-serverNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of Mimir — Persistent Memory Engine

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • DeepMem

    Mem0-compatible persistent memory for AI agents: write facts once, recall them semantically.

    by deepmemteam · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • memra com.usememra/memra

    Persistent memory for AI agents. EU-hosted, privacy-first, hybrid recall, contradiction detection.

    by usememra.com · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • memory com.humaux/memory

    Persistent long-term memory for AI agents: semantic search, knowledge graph, and task canvas.

    by humaux.com · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • Kemory

    Persistent memory for AI agents: connects MCP clients to your Kemory memory vault

    by SeKondBrainAILabs · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • memdata io.github.thelabvenice/memdata

    Persistent memory for AI agents. Store context, retrieve it semantically.

    by thelabvenice · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • mem0 io.github.mem0ai/mem0

    Persistent memory for AI agents: add, search, update, and delete long-term memories.

    by mem0ai · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

Prometheus MCP Server

In its own words, on Official MCP Registry:

MCP server providing Prometheus metrics access and PromQL query execution for AI assistants

Mimir — Persistent Memory Engine

In its own words, on Official MCP Registry:

Persistent memory for AI agents. 36+ MCP tools: encryption, decay, hybrid search, knowledge graph.

How to run each

Prometheus MCP Server As a local MCP server: Docker image

Claude Code
claude mcp add --env "PROMETHEUS_PASSWORD=<YOUR_PROMETHEUS_PASSWORD>" --env "PROMETHEUS_TOKEN=<YOUR_PROMETHEUS_TOKEN>" --env "PROMETHEUS_URL=<YOUR_PROMETHEUS_URL>" --transport stdio prometheus-mcp-server -- docker run -i --rm -e PROMETHEUS_PASSWORD -e PROMETHEUS_TOKEN -e PROMETHEUS_URL ghcr.io/pab1it0/prometheus-mcp-server:1.6.2

Requires: PROMETHEUS_PASSWORD (secret), PROMETHEUS_TOKEN (secret), PROMETHEUS_URL

Mimir — Persistent Memory Engine

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

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

Tools each declares

The marketplaces of Mimir — Persistent Memory Engine publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Mimir — Persistent Memory Engine publish no settings it asks for, so we do not compare settings.

What it can do: Prometheus MCP Server · What it can do: Mimir — Persistent Memory Engine · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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