MCP server setup

Connection details

Replace qr_live_YOUR_KEY with a key from Dashboard → API. Give the assistant a key of its own, so revoking it stops nothing else.

Claude app (web and desktop)

Add the server as a custom connector and sign in. No key needed.

1. 1Open Customize → Connectors, choose Add, then Add custom connector.
2. 2Give it a name and paste the server URL below.
3. 3Keep sign-in on. Under OAuth client, choose Register automatically, then Add.
4. 4Sign in on the QRSalt page that opens and choose the workspace.

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

On Team and Enterprise, an owner adds the connector in Organization settings → Connectors first. To use a key instead, choose No sign in and add the header under Request headers.

Checked against the Claude help centre on custom connectors, read 20 October 2026.

Claude Code

One command, run in the folder of the project you want the server in.

With sign-in

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

1. 1Run the command.
2. 2Start Claude Code, type /mcp, choose qrsalt and sign in.

With an API key

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

It's one line on purpose: a trailing backslash breaks the paste in PowerShell and cmd.

Checked against the Claude Code docs on MCP, read 20 October 2026.

Cursor

Add the server to .cursor/mcp.json for one project, or ~/.cursor/mcp.json for all of them.

With sign-in

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

1. 1Save the file.
2. 2Open Settings → MCP and connect. Cursor opens the QRSalt sign-in page.

With an API key

{
  "mcpServers": {
    "qrsalt": {
      "url": "https://app.qrsalt.com/api/mcp",
      "headers": {
        "Authorization": "Bearer qr_live_YOUR_KEY"
      }
    }
  }
}

Keep a file that holds a key out of version control. Merge the block with any servers already listed.

Checked against the Cursor docs on MCP, read 20 October 2026.

VS Code

Add the server to .vscode/mcp.json and use it from the chat pane in Agent mode.

With sign-in

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

1. 1Save the file.
2. 2Press Start above the server entry and sign in.

With an API key

{
  "inputs": [
    {
      "type": "promptString",
      "id": "qrsalt-key",
      "description": "QRSalt API key",
      "password": true
    }
  ],
  "servers": {
    "qrsalt": {
      "type": "http",
      "url": "https://app.qrsalt.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${input:qrsalt-key}"
      }
    }
  }
}

VS Code asks for the key when you press Start and stores it itself. The file only refers to it, so you can commit it.

Checked against the VS Code MCP configuration reference, read 20 October 2026.

Other clients

Any client that speaks MCP over Streamable HTTP works. If it supports MCP sign-in, give it the URL alone; if not, add the header.

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

Authorization: Bearer qr_live_YOUR_KEY

Tools

13 tools, in the order tools/list returns them. A client only sees the ones its credential's scopes and plan allow.

Both delete tools also need the code's exact name or short-link ending in confirm.

Sign-in and scopes

Building your own client? The full flow, with endpoints and parameters, is in Sign in with QRSalt.

Limits

Troubleshooting