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

> ## Agent Instructions
> The canonical docs host is https://momentic.ai/docs. Append .md to any page URL for clean Markdown. Fetch https://momentic.ai/docs/llms.txt for the page index and https://momentic.ai/docs/llms-full.txt for every page in one file.
> For an unattended setup, first check whether Claude Code already has the Momentic plugin. With the plugin, run `npx --yes @momentic/wizard@latest -y --platform web --editor-tools none` and ignore any CLI skills-install suggestion in its output. Otherwise, run `npx --yes @momentic/wizard@latest -y --platform web --editor-tools skills`. Use `--platform ios` or `--platform android` for mobile. Never run an interactive command in a non-TTY shell.
> Mo is the AI QA engineer, separate from repository YAML tests. With the Momentic plugin, use bundled mo-qa and hosted OAuth by default. Without the plugin, install only mo-qa with `npx -y qa skills --target <agent>`. Keep the requested interface. Otherwise, use hosted tools for web or mobile, including private web targets with an existing Connector. Run sessions that need a new tunnel with the qa CLI. If you can't run commands on the machine that reaches the target, ask the user to start the tunnel there, then use hosted tools unless you lack them or the CLI was requested. For a requested hosted session, use an online Connector and pass its name as access, not a CLI tunnel ID. If none is online, ask the user to run `npx -y qa tunnel start --name <name> <address>` on a machine that reaches the target and wait. Do not run login or tunnel commands for them. For a requested hosted session, report unavailable tools or authentication failures without starting a CLI session. For coding-agent bridge setup, ask the user to complete `npx -y qa login`, then add momentic-hosted as a stdio server running `npx -y qa mcp`. Plugin users must explicitly opt in and disable their hosted plugin entry before adding the bridge. Claude.ai/ChatGPT connectors keep https://mcp.momentic.ai with OAuth. After hosted testing completes, read the report and summarize findings and uncovered requirements. Call `momentic_mo_stop_session` only when the user asks or agrees. For CLI sessions, unless the user wants more testing, export the report, run `qa stop <id> --subagents` even if export fails, then summarize. The CLI is qa, not mo. Docs: https://momentic.ai/docs/mo/quickstart.md.
> Ask the user to complete browser sign-in. For local CLI tools, use the exact MOMENTIC_API_KEY environment variable. If it is absent, ask the user to create a key at https://app.momentic.ai/settings/api-keys and set it in the agent's environment. Never print the key or ask the user to paste it into chat.
> Momentic's capability summary for agents is at https://momentic.ai/docs/skill.md. Claude Code users with the Momentic plugin should use its bundled skills and skip CLI skills installation. Otherwise, run `npx momentic skills -y --target <agent>` or `npx momentic-mobile skills -y --target <agent>`. Both install momentic-test, momentic-maintain, and momentic-spec with web/mobile references. Use the running agent's target. The Momentic plugin also includes mo-qa; qa skills installs only mo-qa.
> Tests are YAML files in the user's repository. Use only the step names listed at https://momentic.ai/docs/reference/commands.md and the file structure at https://momentic.ai/docs/core-concepts/file-format.md. Do not invent step names, config keys, or CLI flags.
> Web tests run on Chromium, iOS tests on simulators, and Android tests on emulators.

# ChatGPT, Claude and Gemini

> Start and follow Mo sessions and review Momentic test runs from ChatGPT, Claude or Gemini with Momentic OAuth. Coding agents use the same server through the Mo skill; CI jobs use the HTTP API, or the `qa` CLI for local and private targets.

Connect ChatGPT, Claude, or Gemini to `https://mcp.momentic.ai`, sign in with
Momentic, and pick a workspace. From the chat you can start [Mo](https://momentic.ai/docs/mo/index.md)
sessions on deployed apps, pull requests, uploaded mobile builds, and private
web apps behind a Connector, review findings, request retests, and list test
runs and quarantines.

* Chat connectors use Momentic OAuth, not API keys. Coding clients can use a
  saved CLI sign-in through `qa mcp`. For CI, use the
  [HTTP API](https://momentic.ai/docs/mo/cli.md#scripts-and-ci).
* Mo's browser runs in the cloud. Hosted sessions reach a private web target
  through an existing [Connector](https://momentic.ai/docs/mo/tunneling.md#run-the-connector-with-docker).
  If none is online, the assistant asks you to run
  `npx -y qa tunnel start --name <name> <address>` on a machine that reaches
  your app, then passes that Connector's name as `access`. It doesn't run
  sign-in or [tunnel](https://momentic.ai/docs/mo/tunneling.md) commands itself.
* Coding agents connect the same server through the
  [Momentic plugin](https://momentic.ai/docs/coding-agents/skills.md#mo) or `install-mcp`, or as a
  [remote MCP server](#other-remote-mcp-clients), and the `mo-qa` skill guides
  its use.
* Connections to `https://mcp.momentic.ai/mo` keep working.

## Connect

Your client plan and workspace policy must allow custom MCP connections.

### Connect ChatGPT

Starting, messaging, or retesting Mo sessions requires write-capable MCP tools
on ChatGPT Business, Enterprise, or Edu, with permission from your workspace.
Pro supports read/fetch tools only. On Business, an admin or owner must add the
server.

In ChatGPT, add Momentic as a custom MCP server:

1. Open [Plugins](https://chatgpt.com/plugins), select the plus button, then
   **Add custom MCP server**.
2. Name it `Momentic`, enter `https://mcp.momentic.ai` as the server URL, and
   configure OAuth authentication. Leave the OAuth client ID and secret empty;
   ChatGPT registers its own client.
3. Select **I understand and want to continue**, then **Create as a plugin**.
4. Install the plugin, sign in with your Momentic account, and start a new
   conversation.

### Claude

Add Momentic as a custom connector:

1. Open **Customize > Connectors**, select **+ Add**, then **Add custom
   connector**.
2. Name it `Momentic`, enter `https://mcp.momentic.ai` as the remote MCP server
   URL, and select **Continue** twice.
3. Under **Authentication**, choose **Sign in now**, select **Add**, and sign in
   with your Momentic account.
4. In a conversation, enable the Momentic connector before asking Claude to use
   it.

On Team and Enterprise plans, an owner adds the connector first; see
[Anthropic's custom connector guide](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp).
To check on sessions without approving each call, set the read-only tools to
**Always allow** in the connector's settings.

### Gemini

> [!NOTE]
>
> Mo's Gemini connection has not yet completed live OAuth verification or Google
> review. These steps describe custom app setup, not a published listing.

Google currently limits custom apps to personal Google Accounts for adults in
the US, in English, with **Keep Activity** on. Work and school accounts aren't
supported. Check
[Google's current requirements](https://support.google.com/gemini/answer/17209137)
before connecting.

1. In the [Gemini web app](https://gemini.google.com), open **Settings >
   Connected Apps**. If needed, open **Personal Intelligence > Connected Apps**.
2. Under **Custom apps**, add `https://mcp.momentic.ai` and select **Next**.
3. Follow the OAuth sign-in flow with your Momentic account and choose a
   workspace. Don't enter a Momentic API key in Google's advanced settings.
4. In a conversation, type `@` and select Momentic to use the connection. After
   web setup, Google also makes custom apps available in its mobile app.

Gemini asks for confirmation before write actions. Review the scope and cost
before approving starts, messages or retests. For files, follow
[credentials and files](#credentials-and-files); a Gemini attachment is not a
ChatGPT MCP file reference.

### Replit

Open
[Add to Replit](https://replit.com/integrations?mcp=eyJkaXNwbGF5TmFtZSI6Ik1vbWVudGljIiwiYmFzZVVybCI6Imh0dHBzOi8vbWNwLm1vbWVudGljLmFpIn0=)
to add Momentic as a custom MCP server, then select **Sign in** next to the
server and sign in with your Momentic account. To add it by hand, open
[Integrations](https://replit.com/integrations), add a custom MCP server named
`Momentic` with the server URL `https://mcp.momentic.ai`, and select **Test &
save**.

### Claude Code

Connect the hosted server and install only the Mo skill:

```bash theme={null}
npx -y qa login
claude mcp add --transport stdio momentic-hosted -- npx -y qa mcp
npx -y qa skills --target claude-code
```

The bridge reuses your saved CLI sign-in. You do not need the plugin or either
local test-authoring server. `mo-qa` uses the hosted server for Mo sessions and
the `qa` CLI when it has to create a tunnel. For Codex, Cursor, Devin, and other
coding agents, [install the Mo skill](https://momentic.ai/docs/coding-agents/skills.md#mo). For CI, use the
[CLI with a key from your secret store](https://momentic.ai/docs/mo/cli.md#scripts-and-ci).

## Ask for a session

Describe the target, the scope, and anything Mo must not do, as you would in a
[brief](https://momentic.ai/docs/mo/brief.md):

```text theme={null}
Test signup on https://staging.example.com using the staging environment and low effort. Don't send real invitations.
```

Sessions appear on the **Sessions** page in the Momentic app, visible to
everyone in your workspace. Each status tells the assistant why the session is
in that state and what to do next.

To send a session's reports and requests for input to your squad's Slack
channel, ask the client to pass `slackChannel` when starting the session. Use a
channel ID or name, with or without `#`. Connect the Momentic Slack app and
invite it to the channel first; an invalid destination rejects the start. This
works for deployed-app and PR sessions.

### Test a pull request

Give the assistant the GitHub PR link, the scope, and an effort:

```text theme={null}
Test https://github.com/acme/store/pull/42 with medium effort. Focus on checkout and don't place orders or send email.
```

PR testing requires the Momentic GitHub App to have access to the repository. Mo
resolves the PR's revisions and deployment preview through that connection. If
no preview is available, provide a deployed preview URL. An environment can
supply test accounts; its base URL is not a substitute for the PR preview. PR
sessions can publish checks and reports to GitHub.

Use an online Connector to reach a local dev server or uncommitted changes. You
can also use a [CLI session](https://momentic.ai/docs/mo/cli.md). A PR link alone doesn't make a local app
reachable.

### Review findings

Ask for findings in a session or across your workspace. Accept a finding,
dismiss it with a reason, or return it to review. Retesting asks Mo to test that
finding again in its existing session and draws from your usage balance.

A completed independent retest marks an Open bug Fixed if it no longer
reproduces, or reopens a Fixed bug if it reproduces. Findings and their history
are preserved. Blocked or incomplete retests, static flags, Needs review and
Dismissed findings keep their status.

You can ask the assistant to mark a finding Fixed, reopen a Fixed bug, or allow
an Open bug for its linked PR run. These are manual decisions, not retests.
Allowing a bug doesn't fix it or allow it in other PR runs. You can remove the
allowance later.

Triage refreshes the existing PR comment and check. Use Momentic's
[triage dialog](https://momentic.ai/docs/mo/triage.md) to review or edit suggested knowledge and manage
tracker issues. The connector doesn't expose those actions.

Choose an existing environment for each run, or supply a preview URL. These
tools do not change saved repository settings or select a deployment status
check. Configure automatic PR testing in Momentic's settings.

## Tool reference

Use these tools on the hosted server for Mo sessions:

| Tool | Use it to |
| - | - |
| `momentic_mo_list_configuration` | Discover environments, online Connectors, and mobile builds. |
| `momentic_mo_start_session` | Start QA for a reachable app or a GitHub PR. |
| `momentic_mo_get_session` | Read progress, questions, the report, or a finding's details. |
| `momentic_mo_list_sessions` | Find your sessions, optionally for a PR. |
| `momentic_mo_message_session` | Answer Mo's questions or steer the existing session. |
| `momentic_mo_stop_session` | Stop a session only when you ask or agree. |
| `momentic_mo_upload_file` | Upload non-secret test data or assets. |
| `momentic_mo_list_findings` | Find bugs across sessions with filters and pagination. |
| `momentic_mo_triage_finding` | Accept, dismiss, mark fixed, reopen, or allow a finding for its PR. |
| `momentic_mo_retest_finding` | Retest one finding in its existing session. |

Three read-only tools cover your workspace's Momentic tests:

| Tool | Use it to |
| - | - |
| `momentic_search_docs` | Search Momentic documentation and return matching sections. |
| `momentic_list_runs` | List recent test runs, filtered by test, branch or status. |
| `momentic_quarantine_list` | List active quarantines and their latest failed run, if any. |

For repository tests, see the
[local MCP tool reference](https://momentic.ai/docs/coding-agents/mcp-server.md#tool-reference).

The hosted tools replace the older `https://api.momentic.ai/mcp` server. Connect
`https://mcp.momentic.ai` instead and remove the old connection.

Reading progress or findings doesn't start work. Starting, messaging, and
retesting can draw from your usage balance and change data on the target site.
Set the scope and prohibited actions before asking Mo to test. Review Mo's
evidence; a session state or an empty findings list isn't a verified pass.

Mo keeps running after a tool call returns. Ask the assistant for an update or
open the session link. The connector doesn't send background chat notifications,
configure schedules or create tracker issues.

## Credentials and files

Name a
[Momentic environment](https://momentic.ai/docs/mo/session-settings.md#reuse-credentials-across-sessions)
in your request to reuse its test accounts and base URL. Values marked
**Sensitive** can't be revealed or copied after saving; Mo uses them by name.
Without an environment, add credentials on the session page with **+** >
**Secret**. Keep passwords and tokens out of chat and file uploads.

The hosted server accepts text content up to 256 KB. ChatGPT clients that
support MCP file attachments can also send binary files. Upload support depends
on the client; a file attached to a conversation isn't necessarily available to
the MCP server. For unsupported files, use the session page or the CLI. Upload
only non-secret test data and assets, not cookies, auth-state files, or .env
files.

Uploading a file doesn't notify Mo. Ask the assistant to send Mo the uploaded
path in the existing session.

## When Mo is blocked

The session status says what stopped Mo:

* **Sign-in page:** add a test account to a Momentic environment and ask the
  assistant to start a new session with it, or add the account on the session
  page and ask the assistant to reply to Mo.
* **Cloudflare:** a workspace admin opens **Settings > Integrations**, selects
  **Connect** next to **Cloudflare**, and completes the connection. Return to
  the session and ask the assistant to reply to Mo if it remains blocked.
* **Other access blockers:** for a firewall or another restriction, follow
  [give Mo access to your site](https://momentic.ai/docs/mo/bot-protection.md), then ask the assistant to
  reply to Mo so it retries.

## Other remote MCP clients

Connect this server in a coding client that doesn't use the Momentic plugin.
`mo-qa` uses it for Mo sessions. If the user explicitly requested hosted tools,
stop and report unavailable tools or authentication failures instead of starting
a CLI session. The `momentic-hosted` name keeps this server separate from the
local `momentic` server. The [Momentic plugin](https://momentic.ai/docs/coding-agents/skills.md) already
includes it.

For Claude Code:

```bash theme={null}
npx -y qa login
claude mcp add --transport stdio momentic-hosted -- npx -y qa mcp
```

For Codex:

```bash theme={null}
npx -y qa login
codex mcp add momentic-hosted -- npx -y qa mcp
```

Complete CLI sign-in before adding the MCP entry. Install the skill with
`npx -y qa skills --target <agent>`, using `claude-code` or `codex` for the
client above.

This doesn't create a tunnel. Hosted sessions reach a private web target through
an online [Connector](https://momentic.ai/docs/mo/tunneling.md#run-the-connector-with-docker); without one,
you start a named tunnel with `qa tunnel start --name` on a machine that reaches
the target. After a failed start, check the original session before starting one
through another connection; the first call may have started Mo.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.