Ext Ops Panel
Open dashboard
Comparison

codex-dispatch vs US Codex

codex-dispatch is a plugin bundle for AI coding tools published by jcardama. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). US Codex is an MCP server published by uscodex.org. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
Marketplacecodex-dispatchUS Codex
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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

codex-dispatch vs US Codex
Factcodex-dispatchUS Codex
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (uscodex.org/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/jcardama/codex-dispatchNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 31 h ago

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

codex-dispatch

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

Codex Dispatch is an agent skill for Claude Code that ensures every Codex MCP dispatch is correct. It enforces the right cwd (target repo, not workspace), sets approval-policy: "never" so Codex never blocks on prompts, picks the right sandbox mode for the task, and requires prompts to be fully self-contained. Covers code review, plan execution, and general repo tasks.

US Codex

In its own words, on Official MCP Registry:

Federal law: US Code, CFR, public laws, bills and executive orders, cross-linked and versioned.

How to run each

codex-dispatch As a Claude Code plugin

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

US Codex As a remote MCP server

Claude Code
claude mcp add --transport http uscodex https://uscodex.org/mcp

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

Only US Codex 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: codex-dispatch · What it can do: US Codex · 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