Skip to main content
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 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.
  • Mo’s browser runs in the cloud. Hosted sessions reach a private web target through an existing Connector. 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 commands itself.
  • Coding agents connect the same server through the Momentic plugin or install-mcp, or as a remote MCP server, 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, 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. To check on sessions without approving each call, set the read-only tools to Always allow in the connector’s settings.

Gemini

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 before connecting.
  1. In the Gemini web app, 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; a Gemini attachment is not a ChatGPT MCP file reference.

Replit

Open Add to Replit 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, 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:
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. For CI, use the CLI with a key from your secret store.

Ask for a session

Describe the target, the scope, and anything Mo must not do, as you would in a brief:
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:
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. 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 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: Three read-only tools cover your workspace’s Momentic tests: For repository tests, see the local MCP 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 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, 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 already includes it. For Claude Code:
For Codex:
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; 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.