io.github.hampsterx/codex-mcp-bridge

NPM · CODEX-MCP-BRIDGE · SCANNED AUG 3

Wraps Codex CLI as MCP tools: codex, review, query, search, structured, ping, listSessions.

Available components

+35 this week 78 78 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security87

No malware found by supply-chain analysis.Pass
Only part of the dependency tree could be resolved (98 of 102), so this covers what we could see, not the whole tree.Partial
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (98 of 102), so this covers what we could see, not the whole tree. View diagnostics → Partial

Provenance & Transparency97

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
Cryptographically verified build provenance (signed, bound to hampsterx/codex-mcp-bridge). View diagnostics → Pass
Clear OSI-approved license (MIT).Pass
Actively maintained (last published 1 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability65

AI-judged instruction clarity (excellent).Pass
Context-footprint check failed: tool/resource definitions use about 1416 tokens (~202/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · codex-mcp-bridge

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add hampsterx-codex-mcp-bridge -- npx -y codex-mcp-bridge

# add to Codex CLI

codex mcp add hampsterx-codex-mcp-bridge -- npx -y codex-mcp-bridge

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hampsterx-codex-mcp-bridge": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "codex-mcp-bridge"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add hampsterx-codex-mcp-bridge --command npx --arg -y --arg codex-mcp-bridge

# ~/.hermes/config.yaml

mcp_servers:
  hampsterx-codex-mcp-bridge:
    command: "npx"
    args: ["-y", "codex-mcp-bridge"]

// mcp.json

{
  "mcpServers": {
    "hampsterx-codex-mcp-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "codex-mcp-bridge"
      ]
    }
  }
}

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

3 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
2 Aug 26 +72
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Provenance: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- The attested source repository moved: hampsterx/codex-mcp-bridge security
- Stability: unverified → 0.23 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: MIT functional
- Package version: 0.8.0 → 0.9.1 functional
1 Aug 26 −20
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
31 Jul 26 −18
- Malware scan: pass → unverified ▼ security
29 Jul 26 +18
- Dependency health: partial → unverified ▼ functional
- Tool coverage: unverified → 100 ▲ functional
28 Jul 26 −18
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- First check of Schema quality: unverified functional
27 Jul 26 43

First indexed and scored.

Show 4 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/[email protected]

Provenance verified

Ecosystem: npm · Outcome: verified

Reason: verified

Source repo:: hampsterx/codex-mcp-bridge
Certificate issuer:: https://token.actions.githubusercontent.com
Certificate SAN:: https://github.com/hampsterx/codex-mcp-bridge/.github/workflows/publish.yml@refs/tags/v0.9.1
Rekor log index:: 2319221413
Predicate type:: https://slsa.dev/provenance/v1
Subject digest:: sha512:6bff58125597584c94849a6d947f27fcdd90625275417dbd65528c866f0ded93850889e8f5c1570efa67784c53b80283c3543dd13a5cf5fa479acb441
Discovery method:: attestation_endpoint

Dependencies 98 packages

98 packages in the resolved dependency tree · 98 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 7 exposed · ~1,416 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

codex Codex CLI ~492

Execute a prompt via Codex CLI. Codex is an AI coding agent that can generate, analyze, refactor, and explain code with full project context (reads AGENTS.md/CODEX.md automatically). Capabilities: code generation and refactoring, code analysis and explanation, file reading and modification (when sandbox allows), git operations and terminal commands, multi-turn conversations via sessionId. When to use a different tool: - For analysis of text you already have (plans, docs, opinions), inline it directly in the prompt rather than passing file paths. The files parameter triggers full file I/O and increases timeout pressure. Tips: - Set workingDirectory to the target repo for project-aware responses. - Use sandbox "read-only" (default) for analysis, "full-auto" for code changes. - Break complex tasks into focused prompts rather than one large request. - Resume multi-turn conversations with sessionId (returned in previous response metadata). - Include relevant files via the files parameter for targeted context (text and images supported). - Set reasoningEffort to control depth: "none" for trivial, "minimal" for lightweight, "low"/"medium" for routine, "high"/"xhigh" for deep analysis.

Input Output Examples

Name	Type	Req	Description
files	array	—	File paths relative to workingDirectory. Supports line ranges: 'path:start-end' (e.g. 'src/lib.rs:900-950'). Text and images supported (images ignore line ranges).
maxResponseLength	integer	—	Soft limit on response length in words
model	string	—	Model to use (e.g. o3, gpt-4.1)
prompt	string	yes	The prompt to send to Codex
reasoningEffort	string	—	Reasoning effort level (maps to -c model_reasoning_effort)
resetSession	boolean	—	Clear this session's conversation history and start fresh (requires sessionId)
sandbox	string	—	Sandbox level: read-only (default), workspace-write, or full-auto (Codex CLI convenience mode for workspace-write with auto-approve)
sessionId	string	—	Session ID to resume a previous conversation
timeout	integer	—	Timeout in milliseconds (default: 60s no files, 180s+30s/file with files, max: 600000)
workingDirectory	string	—	Working directory for the CLI

No output schema declared.

No examples provided.

listSessions List Sessions ~50

List active Codex conversation sessions. Returns session metadata for orchestration (no prompts or responses, just IDs and timing). Use to check available sessions before resuming with the codex tool's sessionId parameter.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ping Health Check ~24

Health check: verifies Codex CLI is installed and authenticated, reports versions and capabilities.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

query Quick Query ~256

Lightweight query for analysis or opinions on text you already have. No file reading, no repo exploration, no session state. Pass text in the context parameter. For code execution or file operations, use the codex tool instead. Use cases: reviewing a plan, critiquing a draft, comparing approaches, answering questions about provided text, generating summaries. Tips: - Pass the text to analyze in the context parameter, not as file paths. - Set reasoningEffort to control depth: "none" for trivial, "minimal" for lightweight, "low"/"medium" for routine, "high"/"xhigh" for thorough analysis. - Use maxResponseLength to control verbosity.

Input Output Examples

Name	Type	Req	Description
context	string	—	Text to analyze (inline, not file paths)
maxResponseLength	integer	—	Soft limit on response length in words
model	string	—	Model to use (e.g. o3, gpt-4.1)
prompt	string	yes	The question or instruction
reasoningEffort	string	—	Reasoning effort level (maps to -c model_reasoning_effort)
timeout	integer	—	Timeout in milliseconds (default: 60000, max: 600000)

No output schema declared.

No examples provided.

review Native Code Review ~255

Run Codex CLI's native diff-aware review via codex exec review --json. The bridge does not accept or bundle a review prompt; upstream Codex owns the reviewer instructions. Use for MCP clients that cannot run shell commands but need native Codex review of uncommitted changes, a base branch diff, or a single commit. Tips: - Set workingDirectory to the target git repository. - Choose mode "uncommitted", "base", or "commit". - Use the codex tool with sandbox "read-only" for free-form review prompts.

Input Output Examples

Name	Type	Req	Description
base	string	—	Base branch or ref. Required when mode is "base".
commit	string	—	Commit SHA or ref. Required when mode is "commit".
mode	string	yes	Diff selector: uncommitted changes, changes against a base branch, or one commit
model	string	—	Model to use (e.g. o3, gpt-4.1)
timeout	integer	—	Timeout in milliseconds (default: 180000, max: 600000)
title	string	—	Optional commit title to display in the review summary
workingDirectory	string	yes	Target git repository directory for native review

No output schema declared.

No examples provided.

search Web Search ~179

Web search via Codex CLI. Searches the web and synthesizes a comprehensive answer with source URLs. Use for current information, documentation lookups, API references, and research questions. Tips: - Ask specific, focused questions for best results. - Results include source URLs for verification. - Use maxResponseLength to control response verbosity. - Default timeout is 2 minutes; increase for complex research queries that may require multiple web fetches.

Input Output Examples

Name	Type	Req	Description
maxResponseLength	integer	—	Soft limit on response length in words
model	string	—	Model to use (e.g. o3, gpt-4.1)
query	string	yes	Search query or question
timeout	integer	—	Timeout in milliseconds (default: 120000, max: 600000)
workingDirectory	string	—	Working directory for the CLI

No output schema declared.

No examples provided.

structured Structured Output ~160

Generate a JSON response conforming to a provided JSON Schema. Use for data extraction, classification, or any task needing machine-parseable output.

Input Output Examples

Name	Type	Req	Description
files	array	—	File paths to include as context (text only, no images). Supports line ranges: 'path:start-end' (e.g. 'src/lib.rs:900-950').
model	string	—	Model to use (e.g. o3, gpt-4.1)
prompt	string	yes	What to generate or extract
schema	string	yes	JSON Schema the response must conform to (as a JSON string)
timeout	integer	—	Timeout in milliseconds (default: 60000)
workingDirectory	string	—	Working directory for file paths

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug