Ext Ops Panel
Open dashboard
Comparison

octo vs thread-keeper

octo is a plugin bundle for AI coding tools published by nyldn. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). thread-keeper is an MCP server published by po4erk91. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
Marketplaceoctothread-keeper
Claude Code: claude-plugins-community Listed
Version: 9.61.0
Forks (GitHub): 402
Stars (GitHub): 4 249
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.13.1
Downloads/month (PyPI): 1 654
Downloads/week (PyPI): 45
Forks (GitHub): 4
Stars (GitHub): 13
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

octo vs thread-keeper
Factoctothread-keeper
Marketplaces that list it11
Stars (GitHub) (differs)4 249 (better)13 (worse)
Forks (GitHub) (differs)402 (better)4 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (threadkeeper)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)41Not published
Parts of the bundle (differs)134Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/nyldn/claude-octopusgithub.com/po4erk91/thread-keeper
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

octo

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

Multi-LLM orchestration for Claude Code and Cowork. Coordinates 8 AI providers (Codex, Gemini, Claude, Perplexity, OpenRouter, Copilot, Qwen, Ollama) through structured Double Diamond workflows with adversarial review and 75% consensus gates. 30+ specialized personas, 40+ slash commands, 50 + skills. Just say what you need — the smart router picks the right workflow.

thread-keeper

In its own words, on Official MCP Registry:

Multi-agent shared brain across Claude, Codex, Antigravity, Gemini, Copilot, and VS Code.

How to run each

octo As a Claude Code plugin

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

thread-keeper As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio thread-keeper -- uvx threadkeeper

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

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

What it can do: octo · What it can do: thread-keeper · 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