Codexbox runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 22 Oct 2026.
Self-hosted MCP server: run OpenAI Codex CLI prompts and manage workspace files.
We read the source, 1 d ago · rules 995398eba69f
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.
const result = spawnSync(process.execPath, args, { stdio: "inherit" });
USER root # codex CLI — pinned npm global install, into a prefix `aicode` owns. # # `codex update` (and the TUI's "Update available!" prompt) shells out to # `npm install -g @openai/codex`, which renames paths in BOTH the global lib # dir and the global bin dir. npm's default…
-v /var/run/docker.sock:/var/run/docker.sock
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.
Markdown linter, workspace-scoped stdio MCP server, and self-hosted text-only remote MCP server.
MCP server bridging AI assistants to OpenAI Codex CLI for code analysis and review
Self-hosted MCP gateway for Codex, Cursor, and Cline with provider-free prompt enhancement.
Create and manage QR codes on me-qr.com from AI clients like Claude and ChatGPT.
Self-hosted MCP task inbox shared by Claude Code, Codex, Gemini CLI and local LLMs.
Safe, self-hosted ZAP operator for guided AI security scans and reports.
Connect MCP clients to local Codex Bridge agents, projects, approvals and workspace tools.
Connect MCP clients to local Codex Bridge agents, projects, approvals and workspace tools.
Answers built from our own checks of this server.