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