---
name: setup
description: Connect Eirberg Store Admin, check staff access and open the admin workspace after installation.
---

Help the user connect the installed Eirberg Store Admin plugin.

1. Inspect the available Eirberg tools and any host-provided plugin or connection status. The staging service at `https://mcp.eirberg.app/mcp` was deployed on 2026-11-04. Keep three states separate: package installed, staff OAuth connection established, and native Medusa permissions verified. Missing tools alone do not establish a service outage or a permission refusal. If the host reports no bundled Eirberg MCP server, diagnose package discovery before asking the user to authenticate. Report the observed connection/discovery error, or say that this chat has no available Eirberg tools when no status is exposed.
2. If the host reports that authentication is required, use its available connection action for the packaged Eirberg server, or give the user the exact connection control and location you can verify in that host. Do not invent menu labels or claim a safety restriction without an actual returned denial. If the host blocks opening the flow, explain that specific refusal and ask the user to open the same supported flow themselves; do not bypass it. The user enters their existing Medusa staging staff email/password and any MFA code only in the sign-in screen. OAuth discovery defaults to read-only access, which is sufficient for setup. Editing requires the host to request `merchant:write` alongside `merchant:read`, followed by explicit write consent and native Medusa permission; do not request that escalation just to test setup. Vitverk-only SSO sessions are not reused; do not provision passwords or staff accounts. Vitverk OS and desktop installers are not prerequisites. An installation using the previous endpoint must update and reconnect. Never handle tokens, passwords, API keys or MFA codes in chat.
3. Once tools are available, call `eirberg_get_capabilities`. Describe the permissions actually returned, including a read-only connection. Do not provision staff or change roles.
4. Call `eirberg_open_admin` to open the workspace. If the current host cannot show it, explain the surface limitation and use available read tools.
5. Verify setup with a bounded read that the user can access. Do not publish, save, upload or alter a record to test the connection.

Use the existing account's native permissions. An MFA refusal requires a supported sign-in flow; never disable or bypass MFA. Installation does not grant access to the store. If the host confirms connection but tools do not appear, ask the user to start a new chat with this plugin selected. If they remain unavailable, report the host, installed package version and redacted connection error for diagnosis; do not present reconnection as completed without evidence.