> ## 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.

# Devin

> Configure Momentic's MCP servers in Devin.

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.

```bash theme={null}
npx -y skills add momentic-ai/skills --all
```

```bash theme={null}
npx -y momentic install-browsers chrome chromium ffmpeg
```

<Tip>
  If your repo already installs `momentic` as part of its dependency install,
  use `npx momentic` instead. It will use the version installed in your repo.
</Tip>

## Step 2: Setup repo prompt

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

```text theme={null}
Configure this repo so future Devin sessions can use Momentic MCP.

Figure out the right place in the repo setup to run these commands at startup:

mkdir -p "$HOME/android-sdk" && curl -sSL -o /tmp/platform-tools.zip https://dl.google.com/android/repository/platform-tools-latest-linux.zip && unzip -q -o /tmp/platform-tools.zip -d "$HOME/android-sdk" && rm /tmp/platform-tools.zip

npx -y skills add momentic-ai/skills --all

Set ANDROID_HOME to /home/ubuntu/android-sdk and make sure adb is available from /home/ubuntu/android-sdk/platform-tools. Set JAVA_HOME to Devin's Java install.

Find where Momentic should run in this project by reading momentic.config.yaml and checking the CI scripts if they are present. Use the browser docs at https://momentic.ai/docs/platforms/web/browsers to decide which browsers this project needs. From that directory, run this once:

npx -y momentic install-browsers chrome chromium ffmpeg

When creating or modifying Momentic tests, use the test creation and manipulation skills under .agents/skills. When investigating previous Momentic results, use the result classification skill under .agents/skills.
```

## 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 the Momentic monorepo is cloned on
the Devin machine. Replace it with the absolute path to your project's
`momentic.config.yaml`.

<Tabs>
  <Tab title="momentic (web)">
    * **Transport type**: STDIO
    * **Command**: `npx`
    * **Arguments** (one per row):

    ```text theme={null}
    -y
    momentic
    mcp
    --config
    /home/ubuntu/repos/[path to your momentic yaml]
    --api-key
    $MOMENTIC_API_KEY
    --daemon
    --headful-browser
    false
    ```

    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](/integrations/mcp-server).
  </Tab>

  <Tab title="momentic-mobile">
    * **Transport type**: STDIO
    * **Command**: `npx`
    * **Arguments** (one per row):

    ```text theme={null}
    -y
    momentic-mobile
    mcp
    --config
    /home/ubuntu/repos/[path to your momentic yaml]
    --api-key
    $MOMENTIC_API_KEY
    --daemon
    --java-home
    /usr/lib/jvm/java-17-openjdk-amd64
    --android-home
    /home/ubuntu/android-sdk
    --headful
    false
    ```

    `--java-home` and `--android-home` set the paths the mobile CLI uses to
    locate Java and `adb`. `/usr/lib/jvm/java-17-openjdk-amd64` is the JDK
    that ships on the Devin base image; `/home/ubuntu/android-sdk` is where
    Step 2 installs Android platform tools. For the full list of available
    flags, see the [mcp command reference](/integrations/mcp-server).
  </Tab>
</Tabs>

## 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_initial_data`, `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.