Authentication and context

Sign in securely and select your Mozark workspace.

Authentication

Mozark MCP uses browser-based sign-in. When the first tool call is made, your client opens the Mozark login page; approve it and you're done. The token is stored by your client — the AI model never sees it.

Your MCP session has exactly the permissions your Mozark user has. If you can't delete a test plan in the Mozark web app, the assistant can't either.

To sign out, remove or disconnect the Mozark server in your client's settings.

Understanding “active context”

Almost every Mozark tool operates inside a hierarchy:

Organisation
 └── App
      └── Project
           └── Test cases, folders, plans, runs, bugs, knowledge base

The MCP server keeps an active context (organisation + project + app) for your session so you don't have to repeat yourself. The assistant resolves it in this order:

1. An ID you explicitly mention in the conversation.

2. A context set earlier this session (mozark_set_active_context or a switch tool).

3. Headers from your client config (X-Mozark-*).

4. Your account's default organisation/project/app from the Admin Control Panel.

5. Nothing — the assistant will ask.

Why the assistant sometimes double-checks. If the only context available is your account-wide default and you belong to more than one organisation, the assistant confirms which one you mean before creating or saving anything. This prevents test cases landing in the wrong project.

Setting or switching context

Just say it in plain language:

You say	What happens
"Use the Acme organisation."	mozark_switch_organization — this also clears project and app, so you'll be asked to pick those next.
"Switch to the Checkout project."	mozark_switch_project (same organisation).
"Use the Android app."	mozark_switch_app (same organisation/project).
"Reset my context."	mozark_clear_active_context.
"What am I working in?"	mozark_get_active_context.