Integrations - Momentic

Test suite

These integrations connect to the tests in your repository and the runs the CLI produces.

• GitHub: install the Momentic GitHub App to post run summaries as pull request comments.
• GitLab: read project, branch, commit, and merge-request metadata with an access token.
• Slack: post a message when a test enters or leaves quarantine, routed per quarantine rule.
• Email: send and receive email from provisioned inboxes inside javascript steps, covering OTP codes, magic links, and receipts.
• SMS: send and receive SMS from provisioned phone numbers inside javascript steps.
• Files: upload and download files during a test.
• Devin: configure Devin sessions to install Momentic, its skills, and the MCP server so sessions can write, run, and repair tests.
• IDE validation: JSON Schemas for autocomplete and inline validation while hand-editing test YAML.

Mo

Use Mo integrations to provide context and start sessions:

• GitHub context: read repository code and pull requests, or select checkouts for the session sandbox.
• GitHub PR comments: mention @momentic-ai with a testing brief and target URL, then follow the session and its Mo check.
• Linear, Notion, and other MCP tools: read issues and specifications, or authorize Mo to update them.
• Linear bug reports: file Mo bugs manually or when you accept them.
• Coding agents: install mo-qa to start sessions, export findings, and recheck fixes from your agent.
• Scripts and CI: start sessions with the CLI or HTTP API, or configure a recurring schedule.
• Files and briefs: attach specifications and test plans to a session.
• Protected and private apps: connect Vercel or Cloudflare, provide sign-in credentials, or reach the target through a tunnel.

Reporting outputs

These are file-format integrations rather than service connections:

• JSON reporter, JUnit, and Playwright-format reports: feed results to any tool that reads them.
• New Relic: ship run metrics to New Relic.
• Self-hosted result viewer: host the result viewer on your own infrastructure.

Jira and Xray

For Jira or Xray, contact support with the task you need: file a bug in Jira, sync test cases, or import execution results into Xray. These tasks need different connections and configuration. Repository tests can export JUnit XML or JSON for a separate import step. These reporters write result files; they do not create Jira issues or sync Xray test cases. Include your Jira deployment type and the required report format when you ask about integration support.