You need the Codex CLI and a running Docker engine. The published integration needs nothing else for its first verified request.

The container is public and available for linux/amd64 and linux/arm64. It does not read a provider key for the default path. Chat stays on a deterministic local fake provider unless a separate, explicit real-provider authorization is supplied.

STEP 01 / REGISTER

Add the pinned MCP server.

Run this command in a terminal. Everything after -- is the stdio server command Codex will start when it opens the MCP connection.

codex mcp add unified-ai-system -- docker run --rm -i ghcr.io/happy520ai/unified-ai-system/mcp-server:0.4.0

Confirm that Codex stored the expected image and arguments before starting a session:

codex mcp get unified-ai-system --json

STEP 02 / INSPECT

Restart Codex and verify the tools.

Open a fresh Codex session after registering the server, then run /mcp verbose in the terminal UI. The connection should report these nine tools:

Gatewaygateway_health, gateway_readiness, gateway_prompt_enhance, gateway_chat
Knowledgeknowledge_readiness
Workflowsworkflow_health, workflow_actions
Workforceworkforce_health, workforce_agents

Existing Codex sessions do not hot-load a newly added project MCP definition. Restarting the session is part of the setup.

STEP 03 / PROVE THE PATH

Enhance a request, then ask for execution evidence.

Paste this as a normal Codex prompt. It first proves provider-free prompt enhancement, then checks the safety boundary before chat.

First use gateway_prompt_enhance to turn "build a small API for my team" into a coding prompt and prove no provider was called. Then check gateway health and readiness, and send MCP_READY through gateway chat only if the gateway proves fake-only mode. Report the selected provider, model, execution mode, and response.
01

Connected

Codex can complete MCP initialize, tools/list, and tools/call.

02

Fake-only

The gateway identifies the local fake provider and fake execution mode.

03

Disposable

The managed gateway and container stop with the MCP session.

EVIDENCE BOUNDARY

Know exactly what the test proves.

A successful run proves that Codex loaded the stdio server, the managed gateway passed its health boundary, and the published fake-provider path returned a response. It also exposes read-only provider-free prompt enhancement plus knowledge, workflow, and workforce inspection surfaces.

ProvedPublished image, MCP connection, nine tools, local prompt enhancement, fake-provider request
Not authorizedPaid providers, workflow execution, agent dispatch, data mutation
Not claimedProduction readiness, L5 autonomy, or AGI

DIAGNOSE / REMOVE

Keep the setup inspectable.

If the server does not appear, confirm Docker first, inspect the stored MCP definition, and use /mcp verbose after a fresh Codex start.

docker info

Remove the entry when you are finished. The next Codex session will no longer start the server.

codex mcp remove unified-ai-system

See the source quickstart for three safe tasks and the official MCP Registry entry for the published package metadata.