QRFLOW.codes is live, and it works inside AI assistants

QRFLOW.codes is live. It is a web app that turns a link, a phone number, a Wi-Fi network or a contact card into a QR code. Anyone can make one and download it right now, with no account and no payment.

It is also one of the few QR services an AI assistant can work inside. Claude, ChatGPT, Cursor, Claude Code, VS Code and Windsurf can each make codes in a QRFLOW account, in plain words. That works on every plan, including the free one.

Made by asking, not by filling in a form

QRFLOW publishes a Model Context Protocol server. That is the piece a service puts up so an AI assistant can act inside it rather than just describe it. The address is https://qrflow.codes/mcp, and it is the same address for every assistant.

Six of them work today, and each takes about a minute to connect:

Claude. Add the address under Customize, then Connectors.
ChatGPT. Turn on developer mode, then add the address.
Claude Code. One command: claude mcp add --transport http qrflow https://qrflow.codes/mcp.
Cursor. Press Add under Settings, then MCP, or put one entry in mcp.json.
VS Code. Run MCP: Add Server, or add one entry to .vscode/mcp.json.
Windsurf. Add one entry under Settings, then Cascade, then MCP.

Each asks for a sign-in the first time and never again. After that, the asking is done the way a person would say it out loud:

Make a QR code for this link, and one for the Wi-Fi in the back room.
Point the code on the table cards at the new menu.
Make forty codes from this spreadsheet, one per table.
How many people scanned the poster code last week.
Pause the code on the old flyer until the sale starts.

Why that beats a picture

An assistant can already draw a QR code without any of this. ChatGPT will write a few lines of Python and hand one back. It scans, and it is frozen the moment it is made. Nothing has a record of it, nobody can repoint it, and no one is counting.

That matters because a QR code carries its data in the pattern itself. A wrong link on a printed batch means a reprint. A menu code from last spring still opens last spring’s menu.

A dynamic code holds a short redirect instead of the destination. The squares on the table card never change. Where they point can change any time, and every scan is counted on the way through. A restaurant prints its table cards once. A real estate sign points at the next listing when the house sells. A hotel puts the house guide on the wall and edits the guide behind it.

So a code made through QRFLOW is a record in an account, not an image in a chat. It shows up in the dashboard beside every other code, tagged with what made it. A code from Claude is never confused with one made by hand. Someone who has never opened an assistant can edit it later from the website.

“People print a code once, and then the link moves,” said the founder. “Fixing that used to mean logging in somewhere and hunting for the right code. Now you can just ask Claude to do it.”

The difference shows up most in bulk. Forty table codes, one per table, each with its own name and its own scan count, is a tedious afternoon by hand. It is one sentence through a connector, and the result is forty real codes rather than forty pictures.

What an assistant can and cannot do

What an assistant may create follows the same plan rules as the website. Nothing is unlocked by going through an assistant, and nothing is withheld.

The sign-in uses OAuth, and the token an assistant receives is bound to the connector it was issued for. The same token is refused by the REST API. A Business account can use an API key as a bearer token instead, for anything scripted.

An assistant sees the codes in the account that signed in, and nothing else.

Where it does not work yet

Four assistants people ask about cannot connect. The Gemini app, Microsoft Copilot, Perplexity and Grok give an ordinary user no way to add a server like this one. QRFLOW publishes a page for each of them saying so plainly, with the nearest thing that does work today.

What it makes

Asked for by hand or by an assistant, the generator covers 56 kinds of code, grouped by the job rather than by format:

A website, plain text, Wi-Fi, a contact card, an email, a call or a text message.
A location, or driving directions to it.
A PDF, a menu, a Google Form, a Drive file, a YouTube video, a calendar event or a Google review.
A profile on any of twelve social networks, and a chat on WhatsApp, Telegram, Signal or Messenger.
A payment link for PayPal, Venmo, Cash App or Bitcoin.
A GS1 Digital Link for retail packaging, carrying a GTIN with its batch and expiry date.

Fifty-five of the 56 are free to make. Only the GS1 code needs a paid plan.

Each kind has a page of its own with the steps written out, because the hard part is rarely the code. It is finding the right link to put inside it. The Google review page explains where a Place ID comes from. The Google Doc page covers the sharing setting that decides whether the document opens at all.

For developers

Business accounts get a REST API described by an OpenAPI document, plus webhooks. There are single-file clients in TypeScript and Python, each one file with no dependencies.

The full reference is published as plain Markdown as well, at llms-full.txt, so an assistant can read all of it before writing a line. Any blog or site can embed the generator with two lines of HTML.

Price and availability

QRFLOW.codes is live now. Making and downloading a static code is free, with no account and no limit on how many. A free code carries a small QRFLOW mark in the corner.

Premium is $4 a month, or $36 a year. It makes codes dynamic, removes the mark, counts every scan, adds logos, frames and SVG export, and connects a link domain of your own.

Business is $29 a month. It adds five seats, five link domains, API keys, webhooks, GS1 codes and higher bulk limits.

Make a QR code at QRFLOW.codes