QRSalt

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)

Reading your account (scope read)

Changing things (scope write)

Deleting (scope delete, never ticked for you)

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):

{

"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:

{

"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

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

• Setup guide and tool reference: https://qrsalt.com/qr-code-mcp-server
• QRSalt: https://qrsalt.com
• MCP Registry entry: io.github.QRSalt/qrsalt-mcp

License

MIT. See LICENSE.