Ext Ops Panel
Open dashboard
Comparison

H2BIS ProjectBrain MCP vs io.github.hlix-ai/hlix

H2BIS ProjectBrain MCP is an MCP server published by h2bis-dev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.hlix-ai/hlix is an MCP server published by hlix-ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-30. 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
MarketplaceH2BIS ProjectBrain MCPio.github.hlix-ai/hlix
Official MCP Registry Listed
Version: 1.1.19
Downloads/month (npm): 203
Downloads/week (npm): 49
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.2.1
Downloads/month (npm): 398
Downloads/week (npm): 35
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

H2BIS ProjectBrain MCP vs io.github.hlix-ai/hlix
FactH2BIS ProjectBrain MCPio.github.hlix-ai/hlix
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (h2bis-mcp)On your machine (@hlix/mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 0Not published
LicenceNot statedNot stated
Repository (differs)github.com/h2bis-dev/h2bis-project-brain-mcpgithub.com/hlix-ai/hlix
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

H2BIS ProjectBrain MCP

In its own words, on Official MCP Registry:

Connect AI agents to H2BIS ProjectBrain - manage projects, use cases, and capabilities via MCP.

io.github.hlix-ai/hlix

In its own words, on Official MCP Registry:

Work with Hlix projects, tasks, cycles, comments, and verified reviews in one workspace.

How to run each

H2BIS ProjectBrain MCP As a local MCP server: npm package

Claude Code
claude mcp add --env "API_BASE_URL=<YOUR_API_BASE_URL>" --transport stdio h2bis-projectbrain-mcp -- npx -y h2bis-mcp

Requires: API_BASE_URL

io.github.hlix-ai/hlix As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio hlix -- npx -y @hlix/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

The marketplaces of io.github.hlix-ai/hlix publish no settings it asks for, so we do not compare settings.

What it can do: H2BIS ProjectBrain MCP · What it can do: io.github.hlix-ai/hlix · 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