qrlia.
MCP Gateway · works with Claude · Cursor · Zed · Claude Desktop

Your QR platform,
controlled by a sentence.

qrlia speaks Model Context Protocol natively. Connect your AI assistant once and mint, design, manage and measure QR codes by asking in plain English — no scripts, no clicks, no context-switching.

Start freeRead the docs
Claude · qrlia MCP connected
Mint 12 vCard QRs for the speaker line-up at our 2026 Innovation Summit. Use each speaker’s photo as the contact avatar, brand the codes lime-on-slate, drop them in a folder called ‘Summit 2026’.
  • ↳ folders_create → Summit 2026
  • ↳ qrs_create ×12 → vCard payloads + designs
  • ↳ scans_aggregate (warm cache)
Done — 12 codes minted in folder Summit 2026, each carrying the speaker’s photo and your lime-on-slate palette. PDF preview ready in your dashboard. Want me to wire a webhook so the team Slack pings on every scan?

Real tool names. Not a mock — these are the same calls the dashboard makes.

What it is

One protocol. Every AI assistant. Your whole QR stack.

Plug it in

One URL plus one API key in your assistant of choice. The connection survives idle sessions and supports streaming responses for long tool calls.

Speak naturally

Forget endpoints, payloads, status codes. Tell the assistant what you want: ‘Make me 50 multilink QRs for the campaign launch with our brand palette.’ It does the rest.

One source of truth

The MCP gateway is the same engine as our REST API. Same schemas, same validation, same idempotency. Whatever the dashboard or your code can do, your assistant can do.

Why it matters

QR ops should feel like a conversation, not a form-filling marathon.

Solo founders & marketers
Every campaign needs codes — and every code needs a brief, a design and analytics.
Your assistant becomes a junior PM. Brief in chat, ship by lunch.
Ops & event teams
Spreadsheets of attendees, locations, menus — manually reproduced as QRs every time.
Drop the sheet in chat. Ask for QRs. Watch your assistant call the tools, you sip coffee.
Developers
One-off scripts to bulk-import, retag or roll codes age into legacy weekly.
Skip the script. Let the assistant orchestrate. Re-run with a different sentence next time.
Why qrlia

MCP-native from day one. Not a plugin tacked on after the fact.

Streamable HTTP transport

No stdio shim. Connect from Claude Desktop, Cursor, Zed, your CI runner — anywhere an HTTPS request can reach. 30-minute sticky sessions and automatic re-init on idle.

Tenant-scoped by design

API keys carry their tenant boundary. An assistant connected to one workspace cannot see, list or touch another. Auth fails closed at session init.

36+ tools, 1:1 with the REST API

qrs_create, designs_update, templates_list, scans_aggregate, members_invite, webhooks_register, keys_rotate — every endpoint you can curl, your assistant can call.

Built for agent loops

Cursor-paginated reads, Idempotency-Key on writes, ETag-on-update — the assistant can iterate, retry and reconcile without writing weird state machines.

In the wild

Things you stop doing by hand.

Bulk vCard mint
“Mint a vCard for everyone in the team CSV, photo from /headshots/<email>.png, lime palette.”
Campaign rollout
“Create 8 multilink QRs — one per region — pointing at /landing/<region>. Stamp this week’s tag on the design.”
Weekly digest
“Pull last 7 days of scans grouped by country and country-top-QR. Format as a Notion-friendly markdown table.”
Domain rollover
“Move every QR currently pointing at old.example.com to new.example.com. Verify each redirect resolves before flipping.”
Brand audit
“List every QR whose design isn’t on the latest brand template. Suggest a one-shot migration plan.”
Webhook bring-up
“Register a Slack webhook on scan.created for #demo-pings. Test-fire it.”

Ship a QR with a sentence.

Free workspace, no credit card. Your MCP key is waiting in the dashboard the moment you sign in.

Start freeOr use the REST API