QRSalt

io.github.QRSaltPublished by GitHub account QRSaltv1.0.0Updated Oct 24, 2026

Make, re-point and track QR codes and short links, and read QR images, from your AI assistant.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowData & Analytics

Overview

AI-generated overview

Remote QRSalt server that lets an assistant create, re-point and track QR codes and short links, and read QR images.

What you can do
Render and read QR images from text, links or an uploaded image file, without saving anything to the account (render scope). List and inspect saved QR codes, short links and folders, and read scan totals and daily series for one code or the whole workspace (read scope). Create codes for links, text, email, phone or SMS, shorten links, re-point, rename, file, tag, pause or resume dynamic codes, and set GS1 Digital Link addresses (write scope). Permanently delete codes or short links and remove GS1 addresses, each requiring the exact name or short-link ending as confirmation (delete scope, off by default).
When to use it
Useful when you want an assistant to generate QR images on the fly, manage a QRSalt workspace of dynamic codes and short links, re-point printed codes to new destinations, or check scan analytics without leaving the chat.
Requirements
A remote Streamable HTTP endpoint; nothing to install. OAuth sign-in on a QRSalt page where you choose a workspace and tick scopes; only a workspace owner or admin can connect. Clients that cannot sign in can send an API key in the Authorization header instead. A Free workspace gets only the two picture tools; the other 11 need the Pro plan.
Before you install
The assistant acts as the person who connected it and can create, change and, if allowed, permanently delete codes and short links. Delete is never pre-ticked; keep it off unless needed. An API key grants the scopes it carries, so make a dedicated key with minimal scopes and keep it out of committed files. Revoke access under Dashboard, API, Connected apps.

Installation

In SourceWeft

  1. Open QRSalt 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/io.github.QRSalt%2Fqrsalt-mcp/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": {
    "qrsalt": {
      "type": "http",
      "url": "https://app.qrsalt.com/api/mcp"
    }
  }
}

README

QRSalt MCP server

Connect your AI assistant to QRSalt, and it can make QR codes and short links, change where they point, tell you how often they were scanned, and read a QR image you send it.

The server is remote. There is nothing to install or run: your assistant talks to

https://app.qrsalt.com/api/mcp

over Streamable HTTP. The first time it connects, a QRSalt page opens in your browser where you sign in, choose a workspace and tick what the assistant may do. If your client can't sign in, it can send an API key instead.

This repository holds the plugin manifests (plugin.json, mcp.json, and copies for Cursor and Claude Code) and the server.json that lists the server in the official MCP Registry as io.github.QRSalt/qrsalt-mcp. The server's code is not here.

What you can ask it

  • "Make me a QR code for tomorrow's open day and show me the picture."
  • "Shorten this link and call it Spring flyer."
  • "Which of my codes still point at the old domain?"
  • "Point the table tent code at the new menu." The printed code stays the same; only its destination moves.
  • "Which code was scanned most last month?"
  • "Pause the trade-show banner code until March."
  • "What's in this QR?" with the image attached.

The 13 tools

What your assistant sees depends on what you allowed when you signed in (or what your key allows), and on your plan. A Free workspace gets the two picture tools. The other 11 come with the Pro plan.

Pictures (scope render, every plan)

ToolWhat it does
render_qr_codeTurns text or a link into a QR image. Nothing is saved.
read_qr_imageReads the text out of a QR image you send as a file. It never fetches a URL.

Reading your account (scope read)

ToolWhat it does
list_codesLists your QR codes and short links, newest first, with scan counts.
get_codeEverything recorded about one code: destination, short link, scans, last scan.
list_foldersYour folders and how many codes are in each.
get_scan_analyticsScan totals and a daily series, for one code or the whole workspace.
get_code_imageThe picture of a saved code, with its colours, shapes and logo.

Changing things (scope write)

ToolWhat it does
create_codeMakes a new code for a link, text, email, phone number or text message.
update_codeRe-points, renames, files, tags, pauses or resumes a dynamic code.
create_short_linkShortens a link. It counts clicks and can be re-pointed later.
set_gs1_linkGives a dynamic code a GS1 Digital Link address for product packaging.

Deleting (scope delete, never ticked for you)

ToolWhat it does
remove_gs1_linkRemoves a code's GS1 Digital Link address.
delete_codeDeletes one code or short link, permanently.

Both deleting tools need the code's exact name or short-link ending as a confirmation, so a vague "delete it" deletes nothing.

Install

Cursor

Install the plugin from cursor.directory, or add the server to .cursor/mcp.json (one project) or ~/.cursor/mcp.json (all projects):

json
{  "mcpServers": {    "qrsalt": {      "url": "https://app.qrsalt.com/api/mcp"    }  }}

Open Settings, then MCP, and connect. Cursor opens the QRSalt sign-in page.

Claude Code

claude mcp add --transport http qrsalt https://app.qrsalt.com/api/mcp

Then run /mcp inside Claude Code, choose qrsalt and sign in.

Or install it as a plugin:

/plugin marketplace add QRSalt/qrsalt-mcp/plugin install qrsalt@qrsalt

Claude app (web and desktop)

  1. Open Settings, then Connectors, and add a custom connector.
  2. Paste https://app.qrsalt.com/api/mcp as the server URL.
  3. Leave the OAuth client ID and secret empty.
  4. Connect, and sign in on the QRSalt page that opens.

VS Code

Add this to .vscode/mcp.json, press Start above the entry and sign in:

json
{  "servers": {    "qrsalt": {      "type": "http",      "url": "https://app.qrsalt.com/api/mcp"    }  }}

Other clients

Any client that speaks MCP over Streamable HTTP can connect with the server URL. Clients that support MCP sign-in find everything else on their own. Clients built for older protocol revisions still work: the server answers initialize in 2025-06-18, 2025-03-26 and 2024-11-05, as well as the current 2026-07-28.

Signing in

The first time your client connects, the server replies that it needs sign-in and says where to find out how. Your client opens a QRSalt page in your browser. There you:

  1. sign in to QRSalt,
  2. choose the workspace,
  3. tick what the assistant may do. Delete is never ticked for you.

Only a workspace owner or admin can connect an assistant, and it acts as the person who connected it. To cut it off, revoke it under Dashboard, API, Connected apps.

For client developers: discovery starts at https://app.qrsalt.com/.well-known/oauth-protected-resource/api/mcp. The authorization server supports OAuth 2.1 with PKCE (S256), dynamic client registration and client ID metadata documents.

Scopes

ScopeBox on the sign-in pageAllows
renderRender imagesDrawing and reading QR images. Nothing is stored or read from your account.
readReadListing codes, links and folders, and reading scans.
writeCreate and changeCreating and changing codes and links.
deleteDeleteDeleting codes and removing GS1 addresses. Off unless you tick it.

Using an API key instead

If your client can set a header but can't sign in, make a key in the QRSalt dashboard under API and send it on every request:

Authorization: Bearer qr_live_YOUR_KEY

For Claude Code:

claude mcp add --transport http qrsalt https://app.qrsalt.com/api/mcp --header "Authorization: Bearer qr_live_YOUR_KEY"

Replace qr_live_YOUR_KEY with your own key. Make a key for the assistant alone and tick only what it needs, so you can revoke it without stopping anything else. Keep it out of files you commit.

What it will not do

  • No tool opens a web address you give it.
  • Nothing touches design, custom domains, team members or billing.
  • Every call runs against the workspace you connected. No tool can name a different one.

Links

License

MIT. See LICENSE.

Source: README.md at commit 24736b4

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 27, 2026

Score

85% 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
  • License10 pts