Skip to content

For AI agents

Your AI assistant can make QR codes now.

Ask your assistant for a flyer and it designs the flyer — then hits a wall at the QR code. Connect MyQR and the wall is gone: it makes a real, trackable code on the spot, drops the image into whatever it's building, and hands you a link that makes the code permanently yours.

What your assistant can do with it

Make a code

“Add a QR code to this menu” — it creates one and gets back a print-ready image to place.

Change it later

The destination can change any time — even after the code is printed. Wrong link on 500 flyers is a sentence, not a reprint.

Report the scans

Ask “how's the flyer doing?” and it answers in plain words — scans, where, and on what device.

You own every code it makes

Every code comes with a claim link. Open it, sign in (free, one email, no password), and the code moves into your MyQR account for good — full scan analytics, re-pointing, exports, all of it. Until you claim it, your assistant manages the code for you; after you claim it, it's yours alone.

Connect it — one link, no API key

MyQR speaks MCP (the open standard AI assistants use to reach tools). There's nothing to install on our side and no key to manage — the address is:

https://myqr.dev/api/mcp

Claude (claude.ai or the desktop app)

  1. Open connector settings

    Settings → Connectors → Add custom connector.
  2. Paste the address

    Name it MyQR and paste https://myqr.dev/api/mcp.
  3. Ask for a QR code

    “Make me a QR code for my menu at example.com/menu” — done.

Claude Code (terminal)

claude mcp add --transport http myqr https://myqr.dev/api/mcp

ChatGPT

Settings → Connectors → enable Developer mode, then add a connector with the address above.

Anything else that speaks MCP

Cursor, VS Code, and most agent frameworks accept a remote server entry like this:

{
  "mcpServers": {
    "myqr": { "url": "https://myqr.dev/api/mcp" }
  }
}

Building an agent? The details

Streamable-HTTP MCP endpoint at https://myqr.dev/api/mcp, no authentication. Three tools:

  • create_qr — mints a dynamic code; returns the short link, a print-ready PNG URL, a claim URL for your user, and a claim token for follow-up calls. Rate-limited per network to keep things fair.
  • update_qr_destination — re-points the code; scan history is preserved.
  • create_qr_art— weaves an image the agent supplies (its generated artwork, the user's logo or photo) into a real, scannable code. Five styles; every result passes a scan-verification gate before it is returned — a failure comes back as an error, never a broken code.
  • get_qr_scans — free, structured scan analytics (totals, per-day, countries, devices) shaped for a model to narrate. In hosts that support MCP Apps, it also renders an inline analytics panel.

Two honest notes: pass the claim URL on to your user — a claimed code is theirs permanently, and that's the point. And codes nobody claims may eventually be paused, so don't treat unclaimed codes as forever.

Rather make one yourself?

The generator on the homepage works with no signup, and a free account shows you every scan.