Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Make, re-point and track QR codes and short links, and read QR images, from your AI assistant.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://app.qrsalt.com/api/mcpRun this in your terminal
claude mcp add --transport http qrsalt https://app.qrsalt.com/api/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"qrsalt": {
"url": "https://app.qrsalt.com/api/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"qrsalt": {
"type": "http",
"url": "https://app.qrsalt.com/api/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://app.qrsalt.com/api/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account QRSalt, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 40 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, LexPact UK Contracts
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Generate UK-law contracts: NDA, service, freelance, recruiter terms of business, IR35.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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 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)
| Tool | What it does |
|---|---|
render_qr_code | Turns text or a link into a QR image. Nothing is saved. |
read_qr_image | Reads the text out of a QR image you send as a file. It never fetches a URL. |
Reading your account (scope read)
| Tool | What it does |
|---|---|
list_codes | Lists your QR codes and short links, newest first, with scan counts. |
get_code | Everything recorded about one code: destination, short link, scans, last scan. |
list_folders | Your folders and how many codes are in each. |
get_scan_analytics | Scan totals and a daily series, for one code or the whole workspace. |
get_code_image | The picture of a saved code, with its colours, shapes and logo. |
Changing things (scope write)
| Tool | What it does |
|---|---|
create_code | Makes a new code for a link, text, email, phone number or text message. |
update_code | Re-points, renames, files, tags, pauses or resumes a dynamic code. |
create_short_link | Shortens a link. It counts clicks and can be re-pointed later. |
set_gs1_link | Gives a dynamic code a GS1 Digital Link address for product packaging. |
Deleting (scope delete, never ticked for you)
| Tool | What it does |
|---|---|
remove_gs1_link | Removes a code's GS1 Digital Link address. |
delete_code | Deletes 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 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 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
https://app.qrsalt.com/api/mcp as the server URL.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" } } }
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.
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:
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.
| Scope | Box on the sign-in page | Allows |
|---|---|---|
render | Render images | Drawing and reading QR images. Nothing is stored or read from your account. |
read | Read | Listing codes, links and folders, and reading scans. |
write | Create and change | Creating and changing codes and links. |
delete | Delete | Deleting codes and removing GS1 addresses. Off unless you tick it. |
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.
io.github.QRSalt/qrsalt-mcpMIT. See LICENSE.