Skip to main content
The explore agent (momentic ai explore) is deprecated. Mo now does the autonomous bug finding. Mo is in private beta, so sign up to get onboarded. To write tests from a code diff, use the MCP server with the momentic-spec skill.
Momentic’s MCP server is a local process that gives a coding agent a live browser or device and tools to browse, edit, run, and triage tests. This page covers the server: installation, the config for each client, and usage tips. The skills teach the agent which tools to call and in what order. Install both.
Requires Momentic CLI 2.54.0 or later.

Prerequisites

  • Momentic CLI installed locally (MCP runs on your machine)
  • A project with a valid momentic.config.yaml
  • A MOMENTIC_API_KEY available to the MCP process (most editors do not inherit your shell environment)

Setup instructions

The fastest path is install-mcp. It detects the coding agents on your machine and writes the server entry into each one’s config. Use momentic-mobile install-mcp for mobile projects; it registers a separate momentic-mobile server, so web and mobile can live in the same config.
See momentic install-mcp for --client, --scope, and noninteractive use. The tabs below show the command for each client and the manual config it writes. Momentic’s MCP is a local stdio server. Every client ultimately runs one of these commands:
Web
Mobile
The tabs below show the web command. For a mobile project, replace momentic with momentic-mobile in the command and use momentic-mobile as the server name. See momentic mcp and momentic-mobile mcp for every supported flag (headful browser, pixel ratio, daemon mode, etc.).
After the server is registered, restart the client and start a new chat. Ask the agent which MCP tools are available. You should see momentic_* tools such as momentic_get_artifacts. If they do not appear, fully restart the client.
Or register the server with the Claude Code CLI:
Verify with claude mcp list. On native Windows, wrap with cmd /c:
Pass MOMENTIC_API_KEY via the CLI’s --env flag or by running the command from a shell that already has it exported. See Claude Code MCP docs for scoping and auth options. Run /mcp to confirm the server is active.

Example prompts

After the server is registered, ask the agent for work that needs a live browser or device:
For longer jobs, invoke a skill by name. The skill tells the agent which tools to call and in what order.

Usage tips

  • Model: use the newest model your editor offers. High reasoning gives the best results; Medium is about 20% faster with some quality loss.
  • Invoke the relevant skill by name when authoring, maintaining, or changing product behavior.
  • Be specific in prompts. For exploratory runs, include a step limit.
  • Let sessions terminate: the agent calls momentic_session_terminate to close the browser. Hard-stopping your editor leaks browser processes.
  • Gitignore .momentic-mcp/. MCP stores screenshots, videos, and traces there.
  • Long-running steps: momentic_preview_step, momentic_preview_steps, and momentic_run_step wait 30 seconds by default, which you can change with timeoutSeconds. Work that takes longer continues in the background and the tool returns a stepRunnerId. Collect the result with momentic_poll_runner, and pass its own timeoutSeconds (0-30, default 0) to hold the poll open instead of busy-polling. Only one preview or run executes per session at a time.