Skip to main content
Use the machine configuration sections below to add the Momentic MCP and Momentic mobile MCP to Devin. Paths use Devin’s Ubuntu user home (/home/ubuntu).

​
Step 1: Update dependencies

Add the following commands to the Update dependencies section of your machine configuration. They install the Momentic skills and the browsers and tooling needed by the Momentic (web) MCP.
For mobile tests, also install the mobile skill:
If your repo already installs momentic as part of its dependency install, use npx momentic instead. It uses the version installed in your repo.

​
Step 2: Setup repo prompt

Click Setup repo, then paste this into Devin’s interactive setup chat:

​
Step 3: Configure MCP servers

Add the MCP server entry in Devin’s MCP servers configuration for each platform you want to use. Use momentic for web tests and momentic-mobile for mobile tests. Both use the STDIO transport. The config path below uses the location where you clone your project on the Devin machine. Replace it with the absolute path to your project’s momentic.config.yaml. Set MOMENTIC_API_KEY in the environment Devin passes to the MCP process, or run momentic login on the configured machine. Stdio arguments are literal; $MOMENTIC_API_KEY in an arguments row is not expanded by a shell.
  • Transport type: STDIO
  • Command: npx
  • Arguments (one per row):
The --daemon flag keeps MCP session tools alive across stdio calls by routing through a local daemon. --headful-browser false disables the visible browser UI inside the Devin VM. For the full list of available flags, see the mcp command reference.

​
Verify

Start a new Devin session in the configured repository and ask the agent which MCP servers are available. It should list each server you configured, and you should see tools whose names start with momentic_ (for example momentic_get_artifacts, momentic_session_start). If tools don’t appear, re-check the MCP arguments and confirm that MOMENTIC_API_KEY is set where Devin starts the MCP server.

​
Fix a failing run

When a cached locator no longer matches, Momentic tries to resolve the target again from its description. If the run still fails, Devin can read the evidence through MCP and investigate the cause.
1

Run the affected tests

Ask Devin to run them from the project directory, for example npx momentic run --labels smoke --upload-results.
2

Point it at the failing step

Name the maintenance skill in the prompt:
The agent reads the failing step’s before and after screenshots, the trace with the DOM, network requests, and console output, and the run history for the branch.
3

Let it decide where the fix belongs

A product bug goes back into the code. A stale locator or an intended behavior change goes into the test file, in the same pull request as the product fix.
See run artifacts and request visual evidence.