Skip to main content
Mobster adds its MCP server to Gemini CLI’s own config. Gemini 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, Gemini CLI included.

​
What it writes

The entry goes in ~/.gemini/settings.json. $GEMINI_CLI_HOME moves the folder. The file holds your other Gemini settings, and Mobster changes only mcpServers.mobster.
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/.gemini/settings.json.

​
Check it

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

​
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. Gemini CLI’s own reference for the file is at https://geminicli.com/docs/tools/mcp-server/.