Skip to main content
Mobster adds its MCP server to Codex CLI’s own config. Codex CLI then lists Mobster’s tools (verify_start, screen, tap, run_tests and the rest of the MCP server).

​
Add it

It prints what it changed:
Add --dry-run to see the change first and write nothing. Run the command again and nothing changes. mobster mcp install --all sets up every agent it finds, Codex CLI included.

​
What it writes

The entry goes in ~/.codex/config.toml. $CODEX_HOME moves the folder. Mobster runs codex mcp add when the codex command is on your PATH, and edits the file otherwise.
Mobster keeps the rest of the file as it is, with a copy of the old one beside it (.mobster-backup). It writes the full path to mobster because apps opened from the Dock don’t see your shell’s PATH, and it never writes a key. --project DIR writes DIR/.codex/config.toml, which Codex reads in a trusted project.

​
Check it

The doctor starts the server the way Codex CLI does, lists its tools and calls status. Then it checks that the Codex CLI entry runs a mobster that exists, and says which command to run if it doesn’t. Start a new Codex session. /mcp lists the server.

​
Add the skill

This copies the mobster skill into ~/.agents/skills, so the agent also knows the verify loop and the rules for a real iPhone: ask before anything that sends, buys, posts or deletes, and never enter a passcode.

​
Take it out

This removes the mobster entry and leaves your other servers alone. Codex CLI’s own reference for the file is at https://learn.chatgpt.com/docs/extend/mcp?surface=cli.