> ## 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, first check whether Claude Code already has the Momentic plugin. With the plugin, run `npx --yes @momentic/wizard@latest -y --platform web --editor-tools none` and ignore any CLI skills-install suggestion in its output. Otherwise, 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, separate from repository YAML tests. With the Momentic plugin, use bundled mo-qa and hosted OAuth by default. Without the plugin, install only mo-qa with `npx -y qa skills --target `. For CLI bridge setup, sign in with `npx -y qa login`, then add momentic-hosted as a stdio server running `npx -y qa mcp` and follow the skill. Plugin users must explicitly opt in and disable their hosted plugin entry before adding the bridge. URL-only Claude.ai/ChatGPT connectors can use https://mcp.momentic.ai with OAuth. For private web targets, discover existing Connectors and pass a Connector name as access. If none is available, ask the user to create a tunnel, then discover its Connector name. Hosted session tools do not accept CLI tunnel IDs. Keep the interface the user requests; ask before switching. For a requested hosted session, report tool or authentication failures without starting a CLI session. The CLI is qa, not mo. Docs: https://momentic.ai/docs/mo/quickstart.md. > Ask the user to complete browser sign-in. For local CLI tools, use the exact MOMENTIC_API_KEY environment variable. If it is absent, ask the user to create a key at https://app.momentic.ai/settings/api-keys and set it in the agent's environment. Never print the key or ask the user to paste it into chat. > Momentic's capability summary for agents is at https://momentic.ai/docs/skill.md. Claude Code users with the Momentic plugin should use its bundled skills and skip CLI skills installation. Otherwise, run `npx momentic skills -y --target ` or `npx momentic-mobile skills -y --target `. Both install momentic-test, momentic-maintain, and momentic-spec with web/mobile references. Use the running agent's target. The Momentic plugin also includes mo-qa; qa skills installs only mo-qa. > 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 > Connect an MCP client to hosted Momentic tools over stdio. Run `qa login` once, then configure your MCP client to launch `qa mcp` (or `npx -y qa mcp`). It forwards the hosted tools without running Mo locally. Stdout is reserved for MCP messages; diagnostics go to stderr. `qa mcp --server ` selects the API server, defaulting to `MOMENTIC_SERVER`, the server saved at login, then production. Production connects to `https://mcp.momentic.ai`; local API servers use `/mo` (for example, `http://localhost:8000/mo`). The selected server must match your saved login. The bridge shares `~/.momentic/auth.json` with the other Momentic CLIs and automatically refreshes the saved WorkOS tokens. No API key is needed. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.