verify_start, screen, tap and run_tests. See the MCP server for the full list.
To add the skill as well, see Editors and Xcode.
Add it
With Mobster for Mac in Applications, open this link in Cursor and confirm: Or add it from the terminal:--dry-run to see the change first and write nothing. Run the command again and nothing changes. Mobster for Mac does the same from Settings › Connectors: Add beside Cursor, under Use Mobster from….
What it writes
The entry goes in~/.cursor/mcp.json, which Cursor reads in every project:
~/.cursor/mcp.json
.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 . writes this repository’s .cursor/mcp.json instead.
Check it
status. On 26 Oct 2026 (Mobster 0.4.0, no key set) its last lines were:
mobster with its tools under MCP.
Check a screen
Build your app for the simulator, then ask Cursor’s agent in your project:verify_start with the app’s path and the expectation. Ask it to drive the simulator with screen and tap. Ask it to finish with verify_finish. verify_finish checks the declared expectations. You get a verdict of passed, failed, needs_review or couldnt_run. You get the report path and an overlay frame when available. No model grades the outcome. Your agent supplies the model access for this loop. The key-less loop
Add the rules and the skill
--rules . writes .cursor/rules/mobster.mdc and a block in AGENTS.md, which tell Cursor’s agent to check its UI changes with Mobster. --with-skill copies the skill into ~/.agents/skills/ios-testing: the verify loop and the rules for a real iPhone, such as asking before anything that sends, buys, posts or deletes. Run it again and nothing changes.
To see your checks and the simulator beside your code, add Mobster’s extension for Cursor and VS Code.
Remove the MCP server
mobster entry and leaves your other servers alone. Add --rules . to take the rules out too. Cursor’s own reference for the file is at https://cursor.com/docs/context/mcp.