Codex Bridge runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 10 Oct 2026.
Connect MCP clients to local Codex Bridge agents, projects, approvals and workspace tools.
We read the source, 1 h ago · rules ccca72095570
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
process = try launchProcess()
const child = spawn(invocation[0], args, {
await copyFile(path.join(extensionRoot, file), path.join(buildRoot, file));
result = subprocess.run(
const inheritedProxies = new Set(Object.keys(process.env)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect MCP clients to local Codex Bridge agents, projects, approvals and workspace tools.
Local-first MCP server for Claude/Codex project wiki and graph workflows
Use Strava's official MCP from Codex and other local stdio clients without a developer app.
Connect Claude, Cursor, Codex, and other MCP clients to manage your Cavuno job board.
Local-first intent and provenance for Codex, Claude Code, Cursor, Gemini CLI, and MCP agents.
Review connected software projects, submit local findings and read reports with explicit approval.
Self-hosted MCP server: run OpenAI Codex CLI prompts and manage workspace files.
Stdio relay connecting Zed, Claude Desktop, Cursor and Codex to NV oOS WordPress MCP endpoints.
Answers built from our own checks of this server.