Skip to main content

Documentation Index

Fetch the complete documentation index at: https://momentic.ai/docs/llms.txt

Use this file to discover all available pages before exploring further.

Starts the Momentic mobile MCP server over stdio. For setup in Cursor, Claude Code, Codex, and other agents, see the MCP integration guide. By default, starting an MCP session opens a localhost page with a remote control UI that allows you to view and interact with the emulator.
npx momentic-mobile mcp [options]

Options

CLI flags override environment variables.
--api-key <key>
string
Authenticates the MCP server with Momentic APIs. Env: MOMENTIC_API_KEY.
-c, --config <path>
string
Points to the momentic.config.yaml file used to load project tests, modules, and environments.
--android-home <path>
string
Sets ANDROID_HOME for the current MCP process. Env: ANDROID_HOME.
--java-home <path>
string
Sets JAVA_HOME for the current MCP process. Env: JAVA_HOME.
--headful [true|false]
string
Whether the remote control browser opens with a visible UI by default. Defaults to true.
--session-idle-timeout-minutes <minutes>
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.
--daemon
boolean
Creates 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 path, enabling multiple MCP servers launched from different directories to resolve to the same project home and share device sessions and other state through a single long-lived process.
Daemon mode is not yet available on Windows. Use the standard stdio mode on Windows for now.