← Back to blog

Manage your QR codes from Claude or ChatGPT: QR Top's MCP server is here

· 3 min read

"Create a QR for each of the restaurant's 20 tables, all pointing to the menu with ?table=N, and give me the list."

In any dashboard in the world, that's the same form twenty times. In Claude or ChatGPT connected to QR Top, it's one sentence. Today we're launching our MCP server, available on every plan — including the free one.

What is MCP?

MCP (Model Context Protocol) is an open standard that lets AI assistants use external tools: instead of just talking about your QRs, the assistant can operate them — with your permission and your API key. It was created by Anthropic (Claude), adopted by OpenAI (ChatGPT) and practically the whole ecosystem, and it's becoming the universal plug between assistants and applications.

QR Top exposes that plug at one URL:

https://qr-top.com/api/mcp

What your assistant can do

Connected to your account, the assistant can:

  • Create dynamic QRs with custom destination, title, and slug (what a dynamic QR is).
  • Change the destination of an already-printed QR — the change is immediate, nothing gets reprinted.
  • Pause or reactivate links.
  • Check statistics: totals, devices, and the daily scan series (how to read that data).
  • Delete links — and here's a detail we care about: the delete tool is flagged as destructive per the standard, so the assistant asks for confirmation before running it.

Three things that used to be tedium and are now one sentence

The batch. "One QR per table", "one QR per billboard", "one QR per sales rep." Any repetitive creation task becomes a single instruction, loop included.

The report. "How did the July campaign scans go? Compare the three bus-stop QRs for me." The assistant pulls each one's stats and summarizes — with conclusions, not just numbers.

The cleanup. "Pause every link with no scans in the last 30 days and tell me which ones." Auditing your account stops being a Sunday afternoon.

How to connect it (one minute)

No keys to copy: the connector uses OAuth and takes you to the QR Top login in your browser.

Claude Code:

claude mcp add --transport http qr-top https://qr-top.com/api/mcp

Then, in your session: /mcp → qr-top → Authenticate. The browser opens, you sign in (or create your account right there), and you're connected.

claude.ai and Claude Desktop: Settings → Connectors → add https://qr-top.com/api/mcp as a custom connector.

Cursor, Windsurf, and similar (mcp.json):

{
  "mcpServers": {
    "qr-top": { "url": "https://qr-top.com/api/mcp" }
  }
}

Prefer a fixed credential for scripts or CI? The endpoint also accepts your usual API key (Settings → API) in the Authorization header.

From there, just ask in plain words.

What you should know first

  • Your account rules everything. The assistant only sees and touches your organization's links, with the same plan and rate limits as the REST API. No magic access.
  • Revocable anytime. OAuth access is tied to your session, and API keys can be revoked from Settings → API.
  • Included on every plan. The free one too, with its 5 dynamic QRs that never expire. Integration access isn't a paid feature at QR Top — what scales with the plan is volume limits.

Create your free account, generate an API key, and try asking your assistant for your first QR. The weird part will be going back to the form.