The whole setup is a URL and a token, pasted into your assistant once. This walks through it for each of the common clients, and explains what the connection can and cannot do.
Create an account to get a token
In the Claude apps, open Settings → Connectors and choose Add custom connector. The server URL is https://mcp.getdynamicqr.com, and your token goes in an Authorization header with the value Bearer followed by a space and the token.
In Claude Code, the same connection is a line in your MCP config: an entry with "type": "http", the url, and the same Authorization header. Your dashboard prints the whole block ready to copy, with a placeholder where the token goes.
Either way, Claude will list the available tools once it connects. If it shows nothing, the token is usually the cause — a revoked one and a mistyped one look identical from the client side.
ChatGPT supports MCP servers as connectors. Add a new one, give it the server URL, and supply the token as a bearer credential when it asks for authentication.
The tools it gets are exactly the ones Claude gets — the server does not know or care which assistant is on the other end, beyond recording the name so your dashboard can tell you what is connected.
These all read a JSON config file listing MCP servers. The block is the same shape in each: a name for the server, "type": "http", the URL, and an Authorization header carrying Bearer and your token.
Your dashboard shows this block filled in for your own install, so it is a copy and one substitution rather than something to assemble by hand. After saving the config, restart the editor — most of them read MCP servers at startup only.
The useful questions are the ones that are awkward in a dashboard:
The assistant will show you each action before it takes it. Re-pointing a code takes effect for every printed copy within seconds.
Three things account for nearly every failure. The token — it is shown once and never again, so a half-copied one is common; make a new one rather than hunting for the old one. The plan — the connection refuses with a readable message on plans that do not include AI assistant access, and your assistant will show you that message. The header — it has to be Authorization: Bearer <token>, with the word Bearer and a space in front.
Your AI Assistants page lists everything that has ever connected, with the time it was last active. If nothing appears there, the handshake never reached us, which points at the URL or the header rather than at anything on this side.
Two things, and one of them takes a click.
AI assistant access rides those two tiers. Everything else here works the same whichever assistant you use.
Made in the dashboard under AI Assistants. Shown once, because only a one-way hash of it is stored — copy it before closing the tab.
This install serves MCP at <code>https://mcp.getdynamicqr.com</code>. Your dashboard shows it again alongside a ready-made config block for editors.
Claude, ChatGPT, Cursor, Windsurf, Zed, Cline — anything that supports custom MCP servers.
Clients this has been set up against.
Five steps, once.
Sign in and open AI Assistants from the dashboard sidebar.
Create a token and name it after the machine or app it will live in.
Copy the token immediately — it is not recoverable afterwards.
In your assistant, add a custom MCP server with our URL and the token as a bearer header.
Ask it "which of my QR codes were scanned this week?" to confirm it works.
Straight answers to what usually decides whether this is the right tool for the job.