> ## 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, 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, a separate product from the YAML test framework: its npm package and CLI are `qa` (not `mo` — `npx mo` is a different project). Install with `npm install -g qa`, authenticate the same MOMENTIC_API_KEY way, install repo skills with `qa skills -y`, and start a session with `qa start "<brief>"` or `qa <url>`. Docs: https://momentic.ai/docs/mo.md.
> You cannot complete the browser sign-in yourself. Read the API key from the exact MOMENTIC_API_KEY environment variable (similarly named vars like BILT_MOMENTIC_API_KEY are ignored), or ask the user to create one at https://app.momentic.ai/settings/api-keys and paste it back.
> Momentic's capability summary for agents is at https://momentic.ai/docs/skill.md. Install the skills with `npx momentic skills --yes` (or `npx momentic-mobile skills --yes` for mobile).
> 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. Physical devices are not supported.

# Use Mo from ChatGPT, Claude and Gemini

> Start and follow Mo sessions from ChatGPT, Claude or Gemini with Momentic OAuth. For coding agents and CI, use the qa CLI and Mo skill.

[Mo](https://momentic.ai/docs/mo/index.md) tests deployed apps and GitHub pull requests from ChatGPT,
Claude or Gemini. Connect through the hosted Model Context Protocol (MCP) server
at `https://mcp.momentic.ai` to start sessions, review findings and request
retests.

Existing connections to `https://mcp.momentic.ai/mo` keep working. Use the root
URL for new connections.

The first time a client connects, you sign in with your Momentic account and
choose the workspace your sessions run in. The server doesn't accept API keys;
for Claude Code, Codex, Cursor, Devin, or CI, use the
[`qa` CLI and Mo skill](https://momentic.ai/docs/coding-agents/skills#mo).

Mo's browser runs in the cloud with either connection. For localhost or private
targets, use the CLI with a [tunnel](https://momentic.ai/docs/mo/tunneling.md). Use one connection per
task.

## Connect

These instructions cover custom connections, not installation from a published
directory listing. Your client plan and workspace policy must allow custom MCP
connections.

### ChatGPT

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

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 Mo 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 credit
use 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.

### Claude Code

Install the Momentic plugin from the skills catalog:

```text theme={null}
/plugin marketplace add momentic-ai/skills
/plugin install momentic@momentic
```

It installs the repository-test skills, local browser and mobile MCP servers,
and the same `mo-qa` skill as `qa skills`. Mo-only work does not require local
MCP setup or local MCP authentication. 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/integrations/scripts-and-ci.md).

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

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

For uncommitted changes or a local dev server, use the [CLI](https://momentic.ai/docs/mo/cli.md) instead. 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 uses Mo credits.

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.

## Hosted tools

All tool names below have the `momentic_mo_` prefix:

| Tool | Use it to |
| - | - |
| `start_session` | Start QA for a reachable app or a GitHub PR. |
| `get_session` | Read progress, questions, the report, or a finding's details. |
| `list_sessions` | Find your sessions, optionally for a PR. |
| `message_session` | Answer Mo's questions or steer the existing session. |
| `stop_session` | Stop a session. |
| `upload_file` | Upload non-secret test data or assets. |
| `list_findings` | Find bugs across sessions with filters and pagination. |
| `triage_finding` | Accept, dismiss, mark fixed, reopen, or allow a finding for its PR. |
| `retest_finding` | Retest one finding in its existing session. |

Reading progress or findings doesn't start work. Starting, messaging, and
retesting can use credits 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/sessions.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

Choose this only if you want hosted MCP in a coding client. Mo-only work uses
the `qa` CLI and skill, so it does not require a second MCP connection or hosted
OAuth sign-in. The `momentic-hosted` name keeps this server separate from the
local `momentic` server.

For example, Codex CLI can connect to `https://mcp.momentic.ai` with OAuth:

```bash theme={null}
codex mcp add momentic-hosted --url https://mcp.momentic.ai
codex mcp login momentic-hosted
```

This doesn't give Mo access to local files, localhost, or private networks. Use
the CLI for those. 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.