codex-mcp-bridge
mcpkey · packageio.github.hampsterx/codex-mcp-bridge · v0.9.1
Wraps Codex CLI as MCP tools: codex, review, query, search, structured, ping, listSessions.
run it
on your own machines, one way per deploy methodgenerated from the record, not tested yet
#!/usr/bin/env bash # codex-mcp-bridge (io.github.hampsterx/codex-mcp-bridge), recipe baremetal (generated). # Generated by Hub for toolset "my-agent"; started by mcp-my-agent-codex-mcp-bridge.service. set -euo pipefail export HOST=127.0.0.1 PORT=8101 exec npx -y supergateway@4 --stdio 'npx -y [email protected]' --outputTransport streamableHttp --stateful --host 127.0.0.1 --port 8101 --streamableHttpPath /mcp --healthEndpoint /healthz [Unit] Description=MCP server codex-mcp-bridge (toolset my-agent), generated by Hub After=network-online.target Wants=network-online.target [Service] Type=simple User=mcp Group=mcp EnvironmentFile=/etc/mcp/my-agent.env Environment=HOME=/var/lib/mcp/codex-mcp-bridge WorkingDirectory=/var/lib/mcp/codex-mcp-bridge ExecStart=/opt/mcp/my-agent/bin/codex-mcp-bridge.sh Restart=on-failure RestartSec=5 NoNewPrivileges=true ProtectSystem=strict ProtectHome=true PrivateTmp=true ReadWritePaths=/var/lib/mcp/codex-mcp-bridge [Install] WantedBy=multi-user.target
generated from the record, not tested yet
docker run --rm -p 127.0.0.1:8101:8000 -e CODEX_CLI_PATH -e CODEX_DEFAULT_MODEL -e CODEX_FALLBACK_MODEL -e CODEX_MAX_CONCURRENT -e CODEX_MCP_SERVERS node:22-alpine sh -c 'npx -y supergateway@4 --stdio '"'"'npx -y [email protected]'"'"' --outputTransport streamableHttp --stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint /healthz'
generated from the record, not tested yet
# Generated by Hub for toolset "my-agent" (2026-10-18T08:11:08+00:00).
# Each package server runs behind a stdio->HTTP bridge and listens on localhost only.
# cp .env.example .env # fill the ${VAR}s
# docker compose up -d && bash smoke.sh
# Remote servers are not here: clients reach them directly (see clients/).
name: mcp-my-agent
services:
codex-mcp-bridge:
image: node:22-alpine
command:
- sh
- -c
- npx -y supergateway@4 --stdio 'npx -y [email protected]' --outputTransport streamableHttp --stateful
--host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint /healthz
ports:
- 127.0.0.1:8101:8000
volumes:
- npm-cache:/root/.npm
healthcheck:
test:
- CMD-SHELL
- wget -qO- http://127.0.0.1:8000/healthz || exit 1
interval: 30s
timeout: 5s
retries: 5
start_period: 2m
restart: unless-stopped
environment:
CODEX_CLI_PATH: ${CODEX_CLI_PATH}
CODEX_DEFAULT_MODEL: ${CODEX_DEFAULT_MODEL}
CODEX_FALLBACK_MODEL: ${CODEX_FALLBACK_MODEL}
CODEX_MAX_CONCURRENT: ${CODEX_MAX_CONCURRENT}
CODEX_MCP_SERVERS: ${CODEX_MCP_SERVERS}
volumes:
npm-cache: {}
uv-cache: {}
generated from the record, not tested yet
# Generated by Hub for toolset "my-agent" (2026-10-18T08:11:08+00:00).
# kubectl create namespace mcp
# kubectl -n mcp create secret generic mcp-credentials --from-env-file=.env
# kubectl apply -f kubernetes.yaml
# Services are cluster-internal: <name>.mcp.svc.cluster.local:8000/mcp. Put an ingress
# with auth in front before exposing any of them.
apiVersion: v1
kind: Namespace
metadata:
name: mcp
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: codex-mcp-bridge
namespace: mcp
labels: &id001
app: codex-mcp-bridge
spec:
replicas: 1
selector:
matchLabels: *id001
template:
metadata:
labels: *id001
spec:
containers:
- name: codex-mcp-bridge
image: node:22-alpine
ports:
- containerPort: 8000
name: http
env:
- name: CODEX_CLI_PATH
valueFrom:
secretKeyRef:
name: mcp-credentials
key: CODEX_CLI_PATH
- name: CODEX_DEFAULT_MODEL
valueFrom:
secretKeyRef:
name: mcp-credentials
key: CODEX_DEFAULT_MODEL
- name: CODEX_FALLBACK_MODEL
valueFrom:
secretKeyRef:
name: mcp-credentials
key: CODEX_FALLBACK_MODEL
- name: CODEX_MAX_CONCURRENT
valueFrom:
secretKeyRef:
name: mcp-credentials
key: CODEX_MAX_CONCURRENT
- name: CODEX_MCP_SERVERS
valueFrom:
secretKeyRef:
name: mcp-credentials
key: CODEX_MCP_SERVERS
command:
- sh
- -c
- npx -y supergateway@4 --stdio 'npx -y [email protected]' --outputTransport streamableHttp
--stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint /healthz
readinessProbe:
httpGet:
path: /healthz
port: http
initialDelaySeconds: 10
---
apiVersion: v1
kind: Service
metadata:
name: codex-mcp-bridge
namespace: mcp
spec:
selector:
app: codex-mcp-bridge
ports:
- port: 8000
targetPort: http
name: http
generated from the record, not tested yet
# Generated by Hub for toolset "my-agent" (2026-10-18T08:11:08+00:00).
# Credentials come from the Secret 'mcp-credentials' (kubectl create secret generic ... --from-env-file=.env).
# Each server under `servers` is one Deployment + Service; the keys after it configure
# upstream charts a worker verified.
servers:
codex-mcp-bridge:
enabled: true
replicas: 1
port: 8000
path: /mcp
container:
name: codex-mcp-bridge
image: node:22-alpine
ports:
- containerPort: 8000
name: http
env:
- name: CODEX_CLI_PATH
valueFrom:
secretKeyRef:
name: mcp-credentials
key: CODEX_CLI_PATH
- name: CODEX_DEFAULT_MODEL
valueFrom:
secretKeyRef:
name: mcp-credentials
key: CODEX_DEFAULT_MODEL
- name: CODEX_FALLBACK_MODEL
valueFrom:
secretKeyRef:
name: mcp-credentials
key: CODEX_FALLBACK_MODEL
- name: CODEX_MAX_CONCURRENT
valueFrom:
secretKeyRef:
name: mcp-credentials
key: CODEX_MAX_CONCURRENT
- name: CODEX_MCP_SERVERS
valueFrom:
secretKeyRef:
name: mcp-credentials
key: CODEX_MCP_SERVERS
command:
- sh
- -c
- npx -y supergateway@4 --stdio 'npx -y [email protected]' --outputTransport streamableHttp
--stateful --host 0.0.0.0 --port 8000 --streamableHttpPath /mcp --healthEndpoint /healthz
readinessProbe:
httpGet:
path: /healthz
port: http
initialDelaySeconds: 10
# helm install my-agent helm/my-agent -n mcp
in the cloud
one click: the provider's deploy form opens filled in, in your own account- koyeb
-
The form opens with CHANGE_ME for each value you supply: CODEX_CLI_PATH, CODEX_DEFAULT_MODEL, CODEX_FALLBACK_MODEL, CODEX_MAX_CONCURRENT, CODEX_MCP_SERVERS. Fill them in before you deploy.
Clients connect to the service's https://…koyeb.app address plus /mcp.
- azure
-
A Container Apps environment with one app per server, each with HTTPS ingress and one replica. The portal asks for each value you supply as a secure parameter; the deployment's outputs list the endpoints.
connect to it
copy what your client needsnpx -y [email protected] # env: CODEX_CLI_PATH, CODEX_DEFAULT_MODEL, CODEX_FALLBACK_MODEL, CODEX_MAX_CONCURRENT, CODEX_MCP_SERVERS
{
"mcpServers": {
"codex-mcp-bridge": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"CODEX_CLI_PATH": "${CODEX_CLI_PATH}",
"CODEX_DEFAULT_MODEL": "${CODEX_DEFAULT_MODEL}",
"CODEX_FALLBACK_MODEL": "${CODEX_FALLBACK_MODEL}",
"CODEX_MAX_CONCURRENT": "${CODEX_MAX_CONCURRENT}",
"CODEX_MCP_SERVERS": "${CODEX_MCP_SERVERS}"
}
}
}
}
#!/usr/bin/env bash
# Registers every server with Claude Code (run once; `claude mcp list` to check).
set -euo pipefail
set -a; [ -f .env ] && source .env; set +a
claude mcp add codex-mcp-bridge -e "CODEX_CLI_PATH=${CODEX_CLI_PATH}" -e "CODEX_DEFAULT_MODEL=${CODEX_DEFAULT_MODEL}" -e "CODEX_FALLBACK_MODEL=${CODEX_FALLBACK_MODEL}" -e "CODEX_MAX_CONCURRENT=${CODEX_MAX_CONCURRENT}" -e "CODEX_MCP_SERVERS=${CODEX_MCP_SERVERS}" -- npx -y [email protected]
{
"mcpServers": {
"codex-mcp-bridge": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"CODEX_CLI_PATH": "${CODEX_CLI_PATH}",
"CODEX_DEFAULT_MODEL": "${CODEX_DEFAULT_MODEL}",
"CODEX_FALLBACK_MODEL": "${CODEX_FALLBACK_MODEL}",
"CODEX_MAX_CONCURRENT": "${CODEX_MAX_CONCURRENT}",
"CODEX_MCP_SERVERS": "${CODEX_MCP_SERVERS}"
}
}
}
}
{
"servers": {
"codex-mcp-bridge": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"CODEX_CLI_PATH": "${CODEX_CLI_PATH}",
"CODEX_DEFAULT_MODEL": "${CODEX_DEFAULT_MODEL}",
"CODEX_FALLBACK_MODEL": "${CODEX_FALLBACK_MODEL}",
"CODEX_MAX_CONCURRENT": "${CODEX_MAX_CONCURRENT}",
"CODEX_MCP_SERVERS": "${CODEX_MCP_SERVERS}"
}
}
}
}
name: my-agent target: local servers: - hub: io.github.hampsterx/codex-mcp-bridge
- not probed yet: tools unpinned, ingest lists them
tools
Not probed yetThe tools appear once the hub or its worker has listed this entry. Running it still works: your client lists them on first start.