cyberian-control vs io.github.robbhimself-1337/claude-army
cyberian-control is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑20.
cyberian-control is a plugin bundle for AI coding tools published by contextualizer-ai. No marketplace we read lists it any more. io.github.robbhimself-1337/claude-army is an MCP server published by robbhimself-1337. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace contextualizer-ai/cyberian | Removed on 2026-10-20 Version: not stated Forks (GitHub): 1 Stars (GitHub): 5 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.3.1 Downloads/month (npm): 138 Downloads/week (npm): 13 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
| Fact | cyberian-controlno longer listed · | io.github.robbhimself-1337/claude-army |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 5 | 1 |
| Forks (GitHub) (differs) | 1 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (claude-army) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/contextualizer-ai/cyberian | github.com/robbhimself-1337/claude-army |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of cyberian-control
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Operate dashboard-launched Claude Code and Codex runs with safe launch, follow-up, stop, resume, model discovery, and persistent run-history workflows.
-
CLI tool for running Claude Code SDK sessions with configurable modes
-
Claude Code operations suite that bundles cross-project prior-work retrieval across code, docs, Skills, meetings, WeChat archives, and conversation history; provider-separated…
-
Meta-tools for running Claude Code well: audit your permission allowlist, fix local toolchain gaps, analyze usage costs, and prune stale saved memories.
-
Bridge multiple Claude Code instances together — share context, send messages, ask and answer questions across sessions without copy-pasting
-
Tools for creating and managing Claude Code plugins, agents, commands, and skills
What each says it does
cyberian-control
Control and coordinate multiple Claude Code sessions via cyberian's agentapi wrapper
io.github.robbhimself-1337/claude-army
Orchestrate multiple Claude Code agents in parallel from chat
How to run each
cyberian-control
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.robbhimself-1337/claude-army As a local MCP server: npm package
claude mcp add --transport stdio claude-army -- npx -y claude-army
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: cyberian-control · What it can do: io.github.robbhimself-1337/claude-army · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.