MCP Gateway · works with Claude · ChatGPT · Cursor · VS Code

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.

Claude · qrlia MCP connected
Make vCard QR codes for the 12 speakers at our 2026 Innovation Summit, using our ‘Speaker card’ template. Names and emails are in the list I pasted.
  • ↳ templates_list → Speaker card
  • ↳ qrs_create_from_template ×12 → one per speaker
  • ↳ qrs_list → check all 12 are live
Done: 12 vCard codes created from your Speaker card template, one per speaker, all active. You can download them from your dashboard. Want me to change any of the contact details?

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

Add one URL to Claude and sign in to your workspace. Scripts and CI can use an API key instead.

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

Claude signs in as you, with your role, and only gets the access you tick: read, write, and admin only if you choose it. It can never reach another workspace. Disconnect any time under Settings → Connected apps.

57 tools for everything you manage in qrlia

Every QR type, edits after print, designs, folders, bulk create, scan analytics, feedback, uploads, barcodes, domains, webhooks and team members, with the same permission checks as the dashboard and the REST API.

Built for agent loops

Cursor-paginated reads, clear error codes, and every tool labelled read-only or destructive, so Claude asks before it deletes anything.

Connect

Two minutes from here to your first QR.

Claude (web, desktop, mobile)

  1. Open qrlia in the Claude directory (claude.ai/directory/connectors/qrlia) and click Connect. Or: Settings → Connectors → Add custom connector, and paste the URL below.
  2. Enter your workspace, sign in, and choose what Claude may do.
https://mcp.qrlia.com/mcp

Claude Code

  1. Run the command below in your terminal.
  2. Type /mcp in Claude Code, pick qrlia, and sign in in the browser window that opens.
claude mcp add --transport http qrlia https://mcp.qrlia.com/mcp

ChatGPT

  1. In ChatGPT, open Settings → Apps, turn on developer mode under Advanced, and create an app with the URL below and OAuth sign-in. Your ChatGPT plan needs to support custom apps.
  2. Enter your workspace, sign in, and allow access. Then ask ChatGPT to use qrlia.
https://mcp.qrlia.com/mcp

Cursor, VS Code, Windsurf, Cline

  1. Add a remote MCP server named qrlia with the configuration below.
  2. The editor opens the qrlia sign-in in your browser.
{ "mcpServers": { "qrlia": { "type": "http", "url": "https://mcp.qrlia.com/mcp" } } }

Scripts, CI and other MCP clients

  1. Create an API key under Settings → API keys (paid plans).
  2. Send it as a bearer token to the same URL. Keep it secret: it acts for the whole workspace or company it was created for.
Authorization: Bearer qrc_…

What Claude can and can't do

  1. It acts as you, with your role. Read access is always included; write and admin are your choice.
  2. Access tokens last an hour and renew quietly; disconnect under Settings → Connected apps.
  3. Questions or a security report: support@qrlia.com.
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. Connect Claude as soon as your workspace exists.