Let your AI assistant manage QR Hero directly

An AI assistant can already explain what a QR code campaign is, or draft copy for a scan-triggered landing page - but ask it to actually create ten codes for a product line, or check how last week's menu code performed, and it hits a wall. Without a way to reach into your actual QR Hero account, every answer stays theoretical: correct in principle, useless for getting the work done.

QR Hero's MCP server closes that gap. Point Claude, Cursor, ChatGPT, Windsurf, VS Code (via GitHub Copilot), or any other MCP-compatible assistant at a scoped token and it gains access to the same 24 tools that power the dashboard and API - codes, domains, analytics, brands, and tokens - callable in plain language. "Create 10 codes for these products" or "how did last week's menu code perform" become requests the assistant can actually carry out, not just discuss.

That access doesn't mean handing over the keys. Bulk or destructive actions preview first, and nothing runs until a second explicit confirm - the same safety model a scoped token already enforces through the dashboard. It's an open standard too, so it isn't locked to one AI vendor, and it's bundled with API access from the Business plan up rather than sold as a separate add-on, with the full tool catalog documented alongside the API reference for teams that want to know exactly what's callable before they connect it.

The MCP integration sits on top of the same API access and Scan analytics endpoints available directly, so an assistant can check scan performance or repoint a Dynamic links destination without a human opening the dashboard.