Ext Ops Panel
Open dashboard
Comparison

Edworking MCP vs io.github.hlix-ai/hlix

Edworking MCP is an MCP server published by Edworking. 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-19. 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
MarketplaceEdworking MCPio.github.hlix-ai/hlix
Official MCP Registry Listed
Version: 0.2.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.2.1
Downloads/month (npm): 620
Downloads/week (npm): 51
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

Edworking MCP vs io.github.hlix-ai/hlix
FactEdworking MCPio.github.hlix-ai/hlix
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last release (differs)2026-10-14Not published
Where it runs (differs)Remote server (mcp.edworking.com/mcp)On your machine (@hlix/mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/edworking/edworking-mcpgithub.com/hlix-ai/hlix
Changes in the last 7 days (differs)20
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)Responded 4 days ago, requires a keyno remote endpoint we check

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

Edworking MCP

In its own words, on Official MCP Registry:

Edworking tasks, Docs, workspace search, conversations and files with scoped OAuth access.

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

Edworking MCP As a remote MCP server

Claude Code
claude mcp add --transport http edworking-mcp https://mcp.edworking.com/mcp

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.

Only Edworking MCP 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

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

What it can do: Edworking 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