Ext Ops Panel
Open dashboard
Comparison

astronomer-data-agents vs CData Connect AI

astronomer-data-agents is a plugin bundle for AI coding tools published by astronomer. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Claude Code: claude-plugins-community). CData Connect AI is an MCP server published by cdata.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
Marketplaceastronomer-data-agentsCData Connect AI
Claude Code: claude-plugins-official Listed
Version: 0.1.0
Forks (GitHub): 69
Stars (GitHub): 452
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 69
Stars (GitHub): 452
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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

astronomer-data-agents vs CData Connect AI
Factastronomer-data-agentsCData Connect AI
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)452No figure on GitHub
Forks (GitHub) (differs)69No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.cloud.cdata.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)2Not published
Parts of the bundle (differs)36Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/astronomer/agentsNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

astronomer-data-agents

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

Data engineering for Apache Airflow and Astronomer. Author DAGs with best practices, debug pipeline failures, trace data lineage, profile tables, migrate Airflow 2 to 3, and manage local and cloud deployments.

CData Connect AI

In its own words, on Official MCP Registry:

Cloud-hosted MCP server for secure AI access to enterprise data sources via CData Connect AI.

How to run each

astronomer-data-agents As a Claude Code plugin

Claude Code
/plugin install astronomer-data-agents@claude-plugins-official

CData Connect AI As a remote MCP server

Claude Code
claude mcp add --transport http cdata-connect-ai https://mcp.cloud.cdata.com/mcp

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

Neither one's marketplaces publish the settings it asks for.

What it can do: astronomer-data-agents · What it can do: CData Connect AI · 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 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