Ext Ops Panel
Open dashboard
Comparison

clickhouse-monitoring vs TimeBase

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

clickhouse-monitoring is a plugin bundle for AI coding tools published by duyet. No marketplace we read lists it any more. TimeBase is an MCP server published by epam. Marketplaces we read that list it: 3 (Official MCP Registry, Copilot CLI: github/awesome-copilot, PyPI (MCP servers)). As of our marketplace pass on 2026-10-24. 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
Marketplaceclickhouse-monitoringTimeBase
Community marketplace duyet/codex-claude-plugins Removed on 2026-10-20
Version: 1.1.1
Forks (GitHub): 1
Stars (GitHub): 15
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.7
Downloads/month (PyPI): 548
Downloads/week (PyPI): 114
Forks (GitHub): 0
Stars (GitHub): 8
Not marked · First seen
Copilot CLI: github/awesome-copilot Not listed Listed
Version: 0.1.7
Forks (GitHub): 0
Stars (GitHub): 7
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 0.2.7
Downloads/month (PyPI): 548
Downloads/week (PyPI): 114
Forks (GitHub): 0
Stars (GitHub): 8
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

clickhouse-monitoring vs TimeBase
Factclickhouse-monitoringno longer listed · TimeBase
Marketplaces that list it (differs)03
Stars (GitHub) (differs)158
Forks (GitHub) (differs)10
Last release (differs)Not published2026-10-22
Where it runs (differs)Installs as a plugin bundleOn your machine (timebase-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published15, secrets among them: 2
Parts of the bundle (differs)18
Licence (differs)Not statedApache-2.0
Repository (differs)github.com/duyet/codex-claude-pluginsgithub.com/epam/timebase-mcp
Changes in the last 7 days (differs)26
First seen (differs)2026-10-162026-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 clickhouse-monitoring

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

  • mcp-clickhouse io.github.infoinlet-marketplace/mcp-clickhouse

    Read-only ClickHouse for AI agents — analytics queries, table inspection, sizes, health.

    by infoinlet-marketplace · MCP server

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

  • clickhouse

    Connect Claude to your ClickHouse Cloud databases. Browse organizations, services, databases, and table schemas. Run read-only SQL queries against your data and get instant…

    by ClickHouse · Plugin bundle

    Listed on: Claude Code: claude-plugins-official, Claude: knowledge-work-plugins, Claude Code: claude-plugins-community · Describes nearly the same job

  • chmonitor

    Read-only ClickHouse monitoring and advice through the chmonitor MCP server, with pointers to its docs and codebase.

    by duyet · Plugin bundle

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

  • WaveHouse Cloud

    Browse, query, and administer your managed WaveHouse + ClickHouse projects (schema, pipes, policy).

    by wavehouse.cloud · MCP server

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

  • Data Observability

    SQL data health analyzer and pipeline observability evaluator.

    by Evozim · MCP server

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

  • CockroachDB

    Enable AI agents to manage, monitor, and query CockroachDB using natural language. Perform complex database operations, cluster management, and query execution seamlessly through…

    by amineelkouhen · MCP server

    Listed on: Docker MCP Catalog · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

clickhouse-monitoring

In its own words, on Community GitHub marketplaces:

Agent Skill for the ClickHouse Monitor dashboard - a real-time monitoring and observability tool. Covers 45 dashboard pages including query monitoring, table management, merge operations, system metrics, security logs, and API integration.

TimeBase

In its own words, on Official MCP Registry:

Explore and query TimeBase streams, schemas, QQL, symbols, and server status via MCP.

How to run each

clickhouse-monitoring

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

TimeBase As a local MCP server: PyPI package

Claude Code
claude mcp add --env "TIMEBASE_OAUTH2_CLIENT_SECRET=<YOUR_TIMEBASE_OAUTH2_CLIENT_SECRET>" --env "TIMEBASE_PASSWORD=<YOUR_TIMEBASE_PASSWORD>" --transport stdio timebase-mcp -- uvx --from "timebase-mcp[all]" timebase-mcp

Requires: TIMEBASE_OAUTH2_CLIENT_SECRET (secret), TIMEBASE_PASSWORD (secret)

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

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

What it can do: clickhouse-monitoring · What it can do: TimeBase · 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/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. Package data comes from the Python Package Index (pypi.org). 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