Skip to main content
Momentic connects to the tools around your tests: where code lives, where CI runs, where you report failures, and where results get discussed. Mo, the QA agent, has its own integrations. Both are listed below.

​
Test suite

These 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: post run summaries as merge request comments 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. Covers 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

Mo’s integrations connect the services a brief or a session needs:
  • GitHub App: read repository context, comment results on pull requests, report a status check, and start scoped runs from PR comments.
  • Confluence: use a Confluence page as the brief.
  • Vercel, Cloudflare, and other hosting providers: bypass deployment protection on the target under test.
  • TestRail, Qase, Testiny: sync Mo’s test cases and report each run’s result to the connected project.
  • Jira, Linear: file an accepted bug as an issue straight from the report.

​
Reporting outputs

These are file-format integrations rather than service connections: