Ext Ops Panel
Open dashboard
Comparison

great-cto vs BridgeAI

great-cto is a plugin bundle for AI coding tools published by avelikiy. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). BridgeAI is an MCP server published by bridgeaibrasil.com.br. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. 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
Marketplacegreat-ctoBridgeAI
Claude Code: claude-plugins-community Listed
Version: 2.95.0
Forks (GitHub): 13
Stars (GitHub): 115
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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

great-cto vs BridgeAI
Factgreat-ctoBridgeAI
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)115 (better)0 (worse)
Forks (GitHub) (differs)13 (better)0 (worse)
Last release (differs)2026-11-11Not published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.bridgeaibrasil.com.br/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)4, secrets among them: 2Not published
Hooks it runs (differs)55Not published
Parts of the bundle (differs)159Not a bundle
LicenceMITMIT
Repository (differs)github.com/avelikiy/great_ctogithub.com/marcoshenriquemaia/bridgeai-plugin
Changes in the last 7 days (differs)60
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (17 h ago)

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

great-cto

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

Full SDLC pipeline with 7 agents: architecture, code review, QA, security. Two decisions per feature, the rest is automated.

BridgeAI

In its own words, on Official MCP Registry:

Hospedagem no Brasil que o agente opera: cria banco, publica, lê log e diz o custo.

How to run each

great-cto As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install great-cto@claude-community

BridgeAI As a remote MCP server

Claude Code
claude mcp add --transport http bridgeai https://mcp.bridgeaibrasil.com.br/mcp

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

Only BridgeAI has a remote endpoint we check. How we check endpoints

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 BridgeAI publish no settings it asks for, so we do not compare settings.

What it can do: great-cto · What it can do: BridgeAI · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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. 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