OpenQR

OpenQR integrations

OpenQR is an API as well as a generator. Generate QR images, create editable dynamic codes, and read scan analytics from your own code, your AI agents, or any no-code tool you already use.

How the API, MCP server and no-code integrations relate

OpenQR isn't three separate products: the REST API, the MCP server and every no-code integration below call the exact same account and the exact same code-creation logic the dashboard uses. Anything you can do by hand, you can automate. Use the REST API if you're writing your own code. Use the MCP server if you want an AI agent (Claude, Cursor or another MCP client) to generate and manage codes from plain English instead of a written integration: it exposes tools such as create_dynamic_qr, update_dynamic_qr, bulk_create_dynamic_qr and get_scans, alongside ones for folders and saved style themes. Use a no-code tool such as Zapier, Make or n8n if you'd rather not write anything: point it at a plain HTTP request and let a trigger do the rest.

  • REST API

    Generate QR images and manage editable dynamic codes with scan analytics over HTTP.

    API docs

  • MCP server

    Let AI agents like Claude create and edit QR codes through the Model Context Protocol.

    MCP guide

  • TypeScript SDK

    A fully typed @open-qr/sdk client for the REST API: install, authenticate, ship.

    View on npm

  • Zapier

    Wire QR generation into 7,000+ apps with no code: trigger on a row, get a code back.

    Invite-only while it's new: add it with the invite link.

    Read the guideAdd to Zapier

  • n8n

    Add QR codes to self-hosted, open-source automation workflows via the OpenQR API.

    Read the guide

  • Make

    Drop QR generation into visual Make scenarios using a plain HTTP module.

    Read the guide

  • Raycast

    Generate and manage dynamic QR codes straight from the Raycast launcher.

    Live on the Raycast Store; open source in raycast/extensions.

    Install on Raycast

Getting started with the OpenQR API, and what people build

Authentication and cost

Every request, whichever of the three you use, authenticates with a single Bearer API key. Create one free in the API dashboard: it's tied to your account, and no card is required. The REST API and MCP server themselves aren't a paid tier; every account gets them. What's gated by plan is how many dynamic codes you can have (1 dynamic code on Free, 25 on Pro) and how far back your scan history goes (7 days on Free, 90 days on Pro, a 12-month window on Business).

What people build with the OpenQR API

Turning a spreadsheet or webhook feed of destination URLs into a QR image for each row, so a hundred product pages or parking bays get a code without opening the dashboard once. Creating dynamic codes whose destination you edit later, so a code printed on a menu or a poster can point somewhere new without reprinting it. And pulling scan counts, top countries, devices and referrers for a code back into your own reporting instead of checking OpenQR's dashboard.

Building your own? Grab the OpenAPI spec or the typed @open-qr/sdk client, then mint a free key in the API dashboard.