Skip to main content
Starts the Momentic mobile MCP server over stdio so coding agents can author, run, and triage iOS and Android tests. See the MCP integration guide for editor-specific setup. By default, sessions open a localhost page with a remote control UI for viewing and interacting with the emulator.
CLI flags override environment variables.

​
Common flags

​
string
Authenticates the MCP server with Momentic APIs. Env: MOMENTIC_API_KEY.
​
string
Path to the momentic.config.yaml file used to load project tests, modules, and environments.

​
Toolchain

​
string
Set ANDROID_HOME for the current MCP process. Env: ANDROID_HOME.
​
string
Set JAVA_HOME for the current MCP process. Env: JAVA_HOME.

​
Session

​
string
Whether the remote control browser opens with a visible UI by default. Defaults to true.
​
boolean
Allow MCP tool responses to include file output references. Defaults to true. Disable for clients that cannot resolve file references.
​
string
Idle timeout for MCP sessions in minutes. Defaults to 5. Sessions inactive for this duration are terminated automatically. Env: MOMENTIC_SESSION_IDLE_TIMEOUT_MINUTES.

​
Caching

​
boolean
Always save updated step caches after successful runs, even on the main and other protected Git branches.
​
boolean
Disable step caches entirely for the MCP session. Steps run without cached data and no caches are saved.
​
boolean
Create a persistent local daemon so mobile sessions can be shared across multiple MCP server invocations. The daemon’s working directory is set to the parent of the config file, so MCP servers launched from different directories share device sessions and other state.
Daemon mode is not yet available on Windows. Use the standard stdio mode on Windows for now.

​
Examples

Start the MCP server using the project’s momentic.config.yaml:
Run with custom Android and Java toolchain paths: