Ext Ops Panel
Open dashboard
Comparison

delegate-to-claude vs Claudebox

delegate-to-claude is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.

delegate-to-claude is a plugin bundle for AI coding tools published by Alec Foster. No marketplace we read lists it any more. Claudebox is an MCP server published by psyb0t. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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

Where each is published
Marketplacedelegate-to-claudeClaudebox
Community marketplace alectivism/cross-model-agent-delegation Removed on 2026-10-16
Version: 2.0.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.5.1
Forks (GitHub): 5
Stars (GitHub): 23
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

delegate-to-claude vs Claudebox
Factdelegate-to-claudeno longer listed · Claudebox
Marketplaces that list it (differs)01
Stars (GitHub) (differs)123
Forks (GitHub) (differs)05
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (docker.io/psyb0t/claudebox:v2.5.1)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/alectivism/cross-model-agent-delegationgithub.com/psyb0t/docker-claudebox
Changes in the last 7 days (differs)40
First seen (differs)2026-10-152026-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 delegate-to-claude

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • create-claude-plugin

    End-to-end skill for creating a Claude Code plugin: scaffold, build, test, host, and submit to the official Anthropic marketplace.

    by codyhxyz · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • claude-handoff

    Auto-generate handoff prompts and restart Claude Code with fresh context

    by amu815 · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • chuck

    Smart context injection for Claude Code — injects relevant rules per prompt, remembers architectural decisions, catches contradictions in real-time

    by cssmith615 · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • claude-cursor-orchestration

    Claude Code + Cursor Agent orchestration system. Delegates coding tasks to Cursor Agent via ACP bridge with Phase 0-8 pipeline.

    by ax-inc-dev · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • claude-code-toolkit

    Reusable architectural rules, skills, agents, and workflows for Claude Code.

    by Berry · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

delegate-to-claude

In its own words, on Community GitHub marketplaces:

Install in Codex. Routes worker tasks out to the Claude Code CLI (Haiku 4.5, Sonnet 5.5, Opus 5.5).

Claudebox

In its own words, on Official MCP Registry:

Self-hosted MCP server exposing Claude Code as an agentic AI tool over streamable HTTP.

How to run each

delegate-to-claude

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Claudebox

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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: delegate-to-claude · What it can do: Claudebox · 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.

Where the data comes from: how the catalog is built