Ext Ops Panel
Open dashboard
Comparison

clickhouse-best-practices vs Lagaam

clickhouse-best-practices is a plugin bundle for AI coding tools published by ClickHouse. Marketplaces we read that list it: 3 (Claude Code: claude-plugins-official, Community GitHub marketplaces, Claude Code: claude-plugins-community). Lagaam is an MCP server published by lagaam-ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-03. 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
Marketplaceclickhouse-best-practicesLagaam
Claude Code: claude-plugins-official Listed
Version: 0.3.0
Forks (GitHub): 38
Stars (GitHub): 564
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Listed
Version: 0.3.0
Forks (GitHub): 38
Stars (GitHub): 564
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.5
Downloads/month (PyPI): 284
Downloads/week (PyPI): 34
Forks (GitHub): 0
Stars (GitHub): 1
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-best-practices vs Lagaam
Factclickhouse-best-practicesLagaam
Marketplaces that list it (differs)3 (better)1 (worse)
Stars (GitHub) (differs)564 (better)1 (worse)
Forks (GitHub) (differs)38 (better)0 (worse)
Last release (differs)2026-10-16Not published
Where it runs (differs)Installs as a plugin bundleOn your machine (lagaam)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published18, secrets among them: 1
Parts of the bundle (differs)8Not a bundle
LicenceApache-2.0Apache-2.0
Repository (differs)github.com/clickhouse/agent-skillsgithub.com/lagaam-ai/lagaam
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

clickhouse-best-practices

In its own words, on Claude Code: claude-plugins-official:

28 best practice rules for ClickHouse schema design, query optimization, and data ingestion — prioritized by impact

Lagaam

In its own words, on Official MCP Registry:

Stops an agent's Trino or Pinot query before it runs if it costs too much or reads outside its grant

How to run each

clickhouse-best-practices As a Claude Code plugin

Claude Code
/plugin install clickhouse-best-practices@claude-plugins-official

Lagaam As a local MCP server: PyPI package

Claude Code
claude mcp add --env "LAGAAM_ALLOWED_TABLES=<YOUR_LAGAAM_ALLOWED_TABLES>" --env "PINOT_PASSWORD=<YOUR_PINOT_PASSWORD>" --transport stdio lagaam -- uvx lagaam

Requires: LAGAAM_ALLOWED_TABLES, PINOT_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-best-practices publish no settings it asks for, so we do not compare settings.

What it can do: clickhouse-best-practices · What it can do: Lagaam · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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