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

# Notion

> Use Notion specifications and test plans as context for Mo sessions.

Give Mo a Notion specification or test plan to derive test cases and acceptance
criteria. Include the page URL and the running app URL in your brief.

## Connect Notion

Add [Notion MCP](https://developers.notion.com/guides/mcp/get-started-with-mcp)
through the [MCP connection setup](/docs/mo/integrations/mcp#connect-a-server):

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

Notion's hosted server requires interactive OAuth. Sign in with an account that
can access the pages Mo needs, then use **Test connection** to review its tools.
Keep **Enabled for Mo** on.

## Test from a specification

Replace the page and app URLs in this brief:

```text theme={null}
Read the checkout specification at https://www.notion.so/acme/checkout-spec.
Test its acceptance criteria on https://preview.example.com.
Do not edit the specification, place an order, or submit payment.
```

The server also exposes tools to create or update content. Specify which writes
Mo may make. Your workspace shares the connection and its saved credentials.
Review the
[provider's permissions and account requirements](https://developers.notion.com/guides/mcp/get-started-with-mcp).

If you can't connect Notion, attach an exported specification or use
[`qa upload`](/docs/mo/cli#move-files) and give Mo 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.