Ext Ops Panel
Open dashboard
Comparison

count-tongulas-workspace vs RepoFuse

count-tongulas-workspace is a plugin bundle for AI coding tools published by alextongme. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). RepoFuse is an MCP server published by repofuse.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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
Marketplacecount-tongulas-workspaceRepoFuse
Claude Code: claude-plugins-community Listed
Version: a4a3185
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.0
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

count-tongulas-workspace vs RepoFuse
Factcount-tongulas-workspaceRepoFuse
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub1
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (repofuse.com/api/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/alextongme/count-tongulas-toolkitgithub.com/dealpatrol/repofuse
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 35 h ago, requires a key

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

count-tongulas-workspace

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

Create team workspaces with shared context across multiple repos. Run /count-tongulas-workspace:create and walk through an interactive setup — enter your team name and repos, and it scaffolds everything: a repo registry (repos.json) with GitHub metadata, a CLAUDE.md with repo map and deployment table, a Makefile with workspace commands, and a bootstrap script that clones all repos. Designed for teams working across many repositories who want Claude Code to understand the full system.

RepoFuse

In its own words, on Official MCP Registry:

Discover and scaffold new apps by reusing code from your GitHub repositories.

How to run each

count-tongulas-workspace As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install count-tongulas-workspace@claude-community

RepoFuse As a remote MCP server

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

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

Only RepoFuse 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: count-tongulas-workspace · What it can do: RepoFuse · 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 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