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

# MCP servers

> Connect MCP servers so Mo can read context and use external tools.

Connect a [Model Context Protocol (MCP)](https://modelcontextprotocol.io/)
server to let Mo read issues and specifications or use the service's other
tools. See the [Linear](/docs/mo/integrations/linear),
[Notion](/docs/mo/integrations/notion), and [Atlassian](/docs/mo/integrations/atlassian)
guides for their hosted endpoints and authentication requirements.

## Connect a server

In **Settings > Integrations**, choose **Add MCP server**:

1. Enter a **Server name** and **Short description** so Mo knows when to use it.
2. Set **Server URL** to the service's public Streamable HTTP endpoint.
3. Choose the authentication method the server requires: **OAuth**, **Headers**,
   or **None**. For OAuth, sign in and grant access. For Headers, enter the
   required header names and values.
4. Open the connection and choose **Test connection** to review its tools. Keep
   **Enabled for Mo** on.

Your Momentic workspace shares each connection and its saved credentials. Review
the connected account's permissions and available tools. MCP tools can write
data: specify whether Mo may create issues or edit documents in your brief. Use
a read-only endpoint or restricted credentials when you only need context.

## Use connected tools

Include the issue ID or document URL and the app URL in your [brief](/docs/mo/brief).
Name the acceptance criteria and any actions to avoid.

For other repository hosts, connect a compatible server or
[upload a diff](/docs/mo/cli#move-files) and include its sandbox path. For services
without a compatible server, attach an exported specification or test plan.

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


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