Sign-in and access

Connecting uses OAuth, the same kind of sign-in as "Sign in with Google". The assistant never sees your password or an API key.

What you see

1. Consent page on mcp.dynaqr.app. It says which assistant wants to use DynaQR, what it will be able to do, and which website will receive its sign-in, for example claude.ai, or "this computer" for Claude Code. Click Continue, or Cancel to stop.
2. Sign in to DynaQR if you aren't already.
3. Connect page (dynaqr.app/connect-mcp). The card is titled "Connect" plus the assistant's name, and names the workspace the assistant will manage. To use a different workspace, switch workspace from the menu first, then come back to this page. Click Allow access.
4. You're sent back to the assistant, which is now connected.

Finish in the same browser within 10 minutes of clicking Continue. If it takes longer, start again from the assistant.

Only owners and admins of a workspace can allow access.

What the assistant gets

Each connection gets its own key for the chosen workspace. The key is stored encrypted on our MCP server. It isn't shown in your browser or to the assistant. It only works through the MCP server, and only for what your plan includes. See which plan you need.

The key acts as the person who allowed access. If that person leaves the workspace, the connection stops working.

More than one workspace

A connection manages one workspace. To manage another, add DynaQR again in the assistant (or disconnect and reconnect) and pick the other workspace on the connect page.

Revoke access

1. In the dashboard, open Integrations.
2. In the API keys card, find the key whose name starts with MCP: followed by the assistant's name. The Last used column shows when it last made a call.
3. Click Revoke and confirm. The assistant loses access immediately.

Removing the connector in the assistant's settings doesn't revoke the key. Revoke it in DynaQR to stop access. You can revoke keys on every plan, including Free.