QRFLOW.codes

codes.qrflowPublished by qrflow.codesOfficial publisherv1.0.0Updated Oct 25, 2026

Create QR codes, re-point printed dynamic codes, name links on your domain, read scan analytics.

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

QRFLOW.codes is a remote MCP server that lets an assistant create QR codes, re-point printed dynamic codes, name links on your domain and read scan analytics.

What you can do
Create QR codes for links or content through the assistant. Re-point dynamic QR codes that have already been printed so the destination changes without reprinting. Name short links on your own domain. Read scan analytics for the codes and links you manage.
When to use it
Useful when you manage QR codes or branded short links and want an assistant to create them, redirect existing printed codes, or pull scan statistics without opening the web dashboard.
Requirements
A remote server reached over streamable HTTP at qrflow.codes; no local package or runtime is needed. Sign-in is through OAuth, so a QRFLOW.codes account is required. No environment variables or headers are declared.
Before you install
The server is authenticated with OAuth and acts on your QRFLOW.codes account. Re-pointing a dynamic code changes where already-printed codes send people, and creating or naming links writes data to your account; confirm destinations before changing them.

Installation

In SourceWeft

  1. Open QRFLOW.codes in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/codes.qrflow%2Fqrflow/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "qrflow-codes": {
      "type": "http",
      "url": "https://qrflow.codes/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.