Ext Ops Panel
Open dashboard
Comparison

io.github.CodeAlive-AI/codealive-mcp vs io.github.selvatuple/revibe-mcp

io.github.CodeAlive-AI/codealive-mcp is an MCP server published by CodeAlive-AI. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.selvatuple/revibe-mcp is an MCP server published by selvatuple. 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
Marketplaceio.github.CodeAlive-AI/codealive-mcpio.github.selvatuple/revibe-mcp
Official MCP Registry Listed
Version: 3.0.3
Forks (GitHub): 9
Stars (GitHub): 91
Not marked · First seen
Listed
Version: 0.1.1
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

io.github.CodeAlive-AI/codealive-mcp vs io.github.selvatuple/revibe-mcp
Factio.github.CodeAlive-AI/codealive-mcpio.github.selvatuple/revibe-mcp
Marketplaces that list it11
Stars (GitHub) (differs)91 (better)1 (worse)
Forks (GitHub) (differs)9 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (ghcr.io/codealive-ai/codealive-mcp:3.0.3)On your machine (revibe-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/codealive-ai/codealive-mcpgithub.com/selvatuple/revibe-mcp
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

io.github.CodeAlive-AI/codealive-mcp

In its own words, on Official MCP Registry:

Semantic code search and analysis from CodeAlive for AI assistants and agents.

io.github.selvatuple/revibe-mcp

In its own words, on Official MCP Registry:

Analyze any codebase — get architecture, file roles, execution flows, and agent context.

How to run each

io.github.CodeAlive-AI/codealive-mcp As a local MCP server: Docker image

Claude Code
claude mcp add --env "CODEALIVE_API_KEY=<YOUR_CODEALIVE_API_KEY>" --transport stdio codealive-mcp -- docker run -i --rm -e CODEALIVE_API_KEY ghcr.io/codealive-ai/codealive-mcp:3.0.3

Requires: CODEALIVE_API_KEY (secret)

io.github.selvatuple/revibe-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "REVIBE_API_KEY=<YOUR_REVIBE_API_KEY>" --transport stdio revibe-mcp -- npx -y revibe-mcp

Requires: REVIBE_API_KEY (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

Only io.github.CodeAlive-AI/codealive-mcp asks for

  • CODEALIVE_API_KEY (secret)

Only io.github.selvatuple/revibe-mcp asks for

  • REVIBE_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: io.github.CodeAlive-AI/codealive-mcp · What it can do: io.github.selvatuple/revibe-mcp · Compare two other plugins

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