native codeLas Vegas, NV · available for work

Can Claude generate QR codes? What you actually get

Short answer

Yes, two ways, and they give you very different things. Asked on its own, Claude writes a little code and hands back an image that’s frozen the moment it’s made. Connected to a QR service through MCP, it makes a real code in an account you own, which you can repoint and count later.

Both answers are real. The difference doesn’t show up until later. A code that works today and a code you can still fix next year look identical on the page.

Which one you get comes down to whether the assistant has a tool to work with.

What you get when you just ask

Ask with nothing connected and you get an image back. The assistant writes a few lines of code, runs them, and hands you a picture.

It usually scans. The pattern is a published standard, so a correctly made one works in any phone camera.

What you can’t do is change it. The address is baked into the squares, so the picture is finished the moment it appears.

There’s also no record of it. Nothing counts the scans, nothing lists it anywhere, and if the page it points at ever moves, the picture is dead. You find out when somebody tells you the code is broken.

That isn’t a flaw in the assistant. It’s what a static code is, whoever makes it.

What a connector changes

A connector hands the assistant a tool it can call, instead of a script it has to write.

With one attached, the same sentence does something different. The code is created in an account that belongs to you. It holds a short link, so the destination lives in the account rather than in the squares.

After that you can ask the assistant to point it somewhere else, pause it, or tell you how many scans it has. The printed squares never change, because there’s nothing in them to change.

The piece that makes this possible is MCP. It’s a standard way for a service to let an assistant act inside it, rather than only describe it.

Where asking an assistant actually pays off

Making one code isn’t the interesting part. Any website does that in a few seconds, and you don’t need an assistant for it.

It pays off in bulk. Fifty codes, one per table, each pointing somewhere different and named so you can tell them apart later. That’s one sentence to an assistant, or an afternoon of clicking.

It pays off again months later, when the thing they point at moves and you’d otherwise be reprinting fifty cards.

When a plain picture is the right answer

Plenty of jobs need none of that, and it’s worth saying so.

The wifi password on a card by the kettle. A link on a slide you’re presenting in ten minutes. A code on a sticker for your own shelf. If the destination will never move and nobody is counting, the picture is the correct tool. An account would just be overhead.

The question that settles it is the same one that settles every QR decision. After this exists, will the destination ever need to move?

If you already printed a frozen one

There’s no way to edit it. The address is in the squares, so you have two real options.

Keep the old destination alive, or reprint. Keeping it alive is usually the cheaper one. Leave something at the old address that sends people to the new place, and every printed code carries on working. The cost is a page you can never delete.

That only works if the old address was yours. If it was a link on somebody else’s domain, the door is shut and reprinting is the only way out.

How to tell which one you got

Look at what came back.

  • An image, or a file to download, and nothing else. That’s the frozen kind.
  • A code in an account, with an id or a link you can refer to again. That’s the other kind.

There’s a faster test if you’re not sure. Ask the assistant to change where the code points. If it offers to make you a new picture, the first one was never editable, and anything already printed stays pointed at the old place.

Where ours fits

QRFLOW.codes publishes a connector for exactly this. Static codes are free, unlimited and need no account, because a code that will never change shouldn’t come with a bill. Saved codes on a paid plan are the editable kind, and an assistant can create, repoint and pause them on your instruction.

It’s one address and one sign-in, and the steps for each assistant are on the product page. The launch announcement covers how the connector works.

Whichever way you make one, decide before it gets printed. Neither kind can change what’s already on the paper.

Where to start

Got a question this did not answer?

Send it over. We read every message ourselves, and the ones that keep coming up get written into their own answer.

Send us a question