Ext Ops Panel
Open dashboard
Comparison

auto-optimize vs io.github.grafana/mcp-grafana

auto-optimize is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑24.

auto-optimize is a plugin bundle for AI coding tools published by donghyungko. No marketplace we read lists it any more. io.github.grafana/mcp-grafana is an MCP server published by grafana. Marketplaces we read that list it: 5 (Official MCP Registry, Claude Code: claude-plugins-official, Docker MCP Catalog, Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-26. 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
Marketplaceauto-optimizeio.github.grafana/mcp-grafana
Community marketplace bluuewhale/auto-optimize Removed on 2026-10-24
Version: 1.0.1
Forks (GitHub): 0
Stars (GitHub): 8
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: v2.1.1
Forks (GitHub): 479
Stars (GitHub): 3 607
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): 479
Pulls (Docker Hub): 1 109 123
Stars (Docker Hub): 22
Stars (GitHub): 3 607
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

auto-optimize vs io.github.grafana/mcp-grafana
Factauto-optimizeno longer listed · io.github.grafana/mcp-grafana
Marketplaces that list it (differs)05
Stars (GitHub) (differs)83 607
Pulls (Docker Hub) (differs)No figure on Docker Hub1 109 123
Forks (GitHub) (differs)0479
Last release (differs)Not published2026-10-20
Where it runs (differs)Installs as a plugin bundleRemote 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)12
Licence (differs)Not statedApache-2.0
Repository (differs)github.com/bluuewhale/auto-optimizegithub.com/grafana/mcp-grafana
Changes in the last 7 days (differs)24
First seen (differs)2026-10-152026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days ago, requires a key

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 auto-optimize

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

  • autoresearch-ai-plugin

    Autonomous experiment loop for Claude Code. Run an endless optimize-measure-keep/discard cycle on any optimization target: LLM training loss, test speed, bundle size, build time…

    by proyecto26 · Plugin bundle

    Listed on: Claude Code: claude-plugins-community, Community GitHub marketplaces · Describes nearly the same job

  • perf

    Structured performance investigation with baselines, profiling, and evidence-backed decisions — run by AI agents inside your editor. `/perf` enforces a rigorous 10-phase…

    by agent-sh · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • evo

    Structured experiment-driven code optimization using tree search and parallel subagents

    by evo-hq · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • performance-optimizer

    Analyze and optimize code performance, identify bottlenecks, and suggest improvements

    by GLINCKER Team · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • codspeed

    CodSpeed is the all-in-one performance testing toolkit. Dive into benchmarking results, flamegraphs, and performance comparisons — give Claude granular profiling context to…

    by CodSpeedHQ · Plugin bundle

    Listed on: Claude Code: claude-plugins-official, Community GitHub marketplaces, Claude Code: claude-plugins-community · Describes nearly the same job

  • performance-benchmarker

    Use this agent for comprehensive performance testing, profiling, and optimization recommendations. This agent specializes in measuring speed, identifying bottlenecks, and…

    by Michael Galpert · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

auto-optimize

In its own words, on Community GitHub marketplaces:

Profiling-driven code optimization workflow. Builds Regression Test and Benchmark Test infrastructure first, then runs an autonomous optimization loop to iteratively improve measurable metrics.

io.github.grafana/mcp-grafana

In its own words, on Official MCP Registry:

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

How to run each

auto-optimize

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

io.github.grafana/mcp-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 io.github.grafana/mcp-grafana has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of auto-optimize publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: auto-optimize · What it can do: io.github.grafana/mcp-grafana · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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. 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