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

# Atlassian

> Read Jira issues and Confluence pages to scope Mo testing.

Give Mo Jira acceptance criteria and Confluence specifications through Atlassian
Rovo MCP. Your connected account's permissions determine which pages, issues,
and tools Mo can access.

## Connect Jira and Confluence

Add
[Atlassian Rovo MCP](https://developer.atlassian.com/cloud/rovo-mcp/guides/getting-started/)
through the [MCP connection setup](/docs/mo/integrations/mcp#connect-a-server):

| Setting | Value |
| - | - |
| Server URL | `https://mcp.atlassian.com/v2/mcp` |
| Authentication | **OAuth** |

Sign in, grant access, and use **Test connection** to review the available
tools. Keep **Enabled for Mo** on. Your Momentic workspace shares the connection
and its saved credentials.

## Test from an issue

Include the issue or document reference and the running app URL in your brief:

```text theme={null}
Read Jira issue SHOP-412 and its linked Confluence specification.
Test the acceptance criteria on https://preview.example.com.
Do not edit Jira or Confluence, place an order, or submit payment.
```

Review the
[provider's account requirements and permissions](https://developer.atlassian.com/cloud/rovo-mcp/guides/getting-started/).
Specify whether Mo may use tools that write data.

The native **Atlassian** connection in **Settings > Integrations** files issues
from repository test results. Connect Rovo MCP to let Mo read Jira and
Confluence during a session. If you can't connect it, attach an exported spec or
[upload one](/docs/mo/cli#move-files) and include its sandbox path.

See [Mo integrations](/docs/mo/integrations) for other connections.


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