Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

QRX

by qrxcodesversion 1.2.4i★ –iComputer or cloud
Registry namecodes.qrx/mcp

Install

Overview

Description from the maker (original English)

Turn a prompt and a link into a branded, print-ready QR code that always scans.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Computer or cloud
  • Transport: stdio, Streamable HTTP
  • Category: Other
  • You need to fill in: QRX_API_KEY, Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • You fill in yourself: QRX_API_KEY, Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • Runs in the cloudNothing to install; it connects over the internet
  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "qrx": {
      "command": "npx",
      "args": [
        "-y",
        "@qrxcodes/mcp"
      ],
      "env": {
        "QRX_API_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add --transport http qrx https://qrx.codes/mcp --header 'Authorization: Bearer {qrx_api_key}'

Or run it on your computer

claude mcp add qrx --env QRX_API_KEY=your-value -- npx -y @qrxcodes/mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "qrx": {
      "url": "https://qrx.codes/mcp",
      "headers": {
        "Authorization": "Bearer {qrx_api_key}"
      }
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "qrx": {
      "command": "npx",
      "args": [
        "-y",
        "@qrxcodes/mcp"
      ],
      "env": {
        "QRX_API_KEY": "your-value"
      }
    }
  }
}

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.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "qrx": {
      "type": "http",
      "url": "https://qrx.codes/mcp",
      "headers": {
        "Authorization": "Bearer {qrx_api_key}"
      }
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "qrx": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@qrxcodes/mcp"
      ],
      "env": {
        "QRX_API_KEY": "your-value"
      }
    }
  }
}

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.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • QRX_API_KEY secret env
    Your QRX API key (qrx_…) from https://qrx.codes/developers/keys. Needed to use the tools; without it the server starts and lists them.
  • Authorization secret HTTP header
    Optional. Connecting needs sign-in or an API key. Clients that support MCP sign-in (OAuth) need no header; otherwise send your QRX API key from https://qrx.codes/developers/keys as a bearer token.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

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

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain qrx.codes (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

  • More stars than 0% of the other 32464 servers in this category
  • Published to the registry more recently than 59% of the other 32464 servers in this category
  • Basic checks equal to or better than 100% of the other 32464 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is QRX safe?

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.

What keys or codes does it need?

You need to fill in: QRX_API_KEY, Authorization

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.2.4) reached the registry 28 days ago.

Which apps can use it?

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.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, yontu

Alternatives

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

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

yontu

by senrecep

Türkçe yazı denetimi: TDK kuralları, yapay zekâ izleri, metin türüne göre üslup.

Runs on your computerUpdated today
Install

README from the maker

Open the README

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.

QRX

Art QR codes that always scan.

QRX makes branded, print-ready QR codes for posters, menus, packaging and signage. Describe the look you want and give it a link: QRX paints the code into artwork, checks that it decodes before handing it over, and points it at a hosted short link, https://qrx.to/ on qrx.codes, that you can re-point later on a paid plan. This repository connects QRX to Claude, ChatGPT, Cursor, VS Code and other MCP clients through the remote server at https://qrx.codes/mcp.

Listed in the official MCP Registry as codes.qrx/mcp.

The QRX logo is a QRX code. Point your phone at it.

What you can do

  • Make a code: "Make a QR code for https://example.com/menu that looks like a watercolour café street."
  • Check on it: generation usually takes under a minute; the agent waits for it and returns the image and short link.
  • Find old codes: list the codes on your account, newest first.
  • Re-point a code: send an existing printed code to a new link, with no reprint (on a paid plan).
  • Check your allowance: see how many codes you have left today.

Connection details

Server URLhttps://qrx.codes/mcp
TransportStreamable HTTP (stateless)
AuthRequired to connect. Sign in with your QRX account (MCP authorization, OAuth 2.1); clients that support it need only the URL. The authorization server is https://clerk.qrx.codes (dynamic client registration or client ID metadata documents, PKCE S256, refresh tokens); scopes qrx:read qrx:generate
Auth with an API keyAuthorization: Bearer qrx_… (preferred), or X-API-Key: qrx_… for clients that can't add the Bearer prefix. If both are sent, Authorization wins. For clients without sign-in, scripts and CI
Without authEvery request, including initialize, answers 401 with a WWW-Authenticate header pointing at https://qrx.codes/.well-known/oauth-protected-resource/mcp, so the client asks you to sign in as soon as it connects
Public tool listhttps://qrx.codes/.well-known/mcp/server-card.json
Docsqrx.codes/developers/mcp (public: server URL, client set-up, tools, limits, privacy)

Sign in or use an API key

Every client below that takes a URL signs in with your QRX account: add the URL, then sign in (free) when the client asks as it connects. There is nothing to copy or keep secret.

For clients that only run local servers, and for scripts and CI, use an API key. Any client below can use one instead of signing in:

  1. Sign in at qrx.codes (free).
  2. Open qrx.codes/developers/keys and create a key. It starts with qrx_.
  3. Keep it secret. The examples below read it from an environment variable called QRX_API_KEY wherever the client allows that:
   # macOS / Linux

export QRX_API_KEY="qrx_live_…"

   # Windows PowerShell (current user, persistent)

Revoke a key at any time from the same page.

Install

Claude Code

Option A: plugin (MCP server, the QRX skill and the code card)

/plugin marketplace add qrxcodes/qrx-mcp

/plugin install qrx@qrx

Then run /mcp, select qrx and sign in to QRX. The plugin also adds the qrx skill, which teaches Claude how to write good art prompts, wait for the code and prepare it for print.

The plugin also shows each finished code in the transcript, under the QRX tool call: its picture, the short link it scans to and a link to its QRX page, with a line while the code is still being painted. It is a mod, so it draws in the terminal (Claude Code 2.1.287 or later) and the Desktop app's Code tab; it fetches the picture with curl. Terminals with kitty graphics (kitty, Ghostty) show the full picture; other terminals show it in coloured character cells, with a link to the full-quality image.

Option B: MCP server only

claude mcp add --transport http qrx https://qrx.codes/mcp --scope user

Then run /mcp, select qrx and sign in. Or commit this to a project's .mcp.json so the whole team gets it (each person signs in to their own account):

{

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

With an API key instead (for example with claude -p or in CI):

claude mcp add --transport http qrx https://qrx.codes/mcp \

--header "Authorization: Bearer $QRX_API_KEY" --scope user

A configured Authorization header replaces sign-in; remove it to sign in instead.

Claude (claude.ai and Claude Desktop): custom connector

Claude Desktop uses the same connector settings as claude.ai; you don't edit claude_desktop_config.json for a remote server.

  1. Open Customize → Connectors, select + Add, then Add custom connector. On Team and Enterprise, an Owner adds it under Organization settings → Connectors first, and each member then selects Connect.
  2. Name: QRX. URL: https://qrx.codes/mcp.
  3. Authentication: Sign in now, then sign in to QRX when Claude asks.
  4. Save, then turn QRX on in a chat from the connectors menu.

With an API key instead, choose No sign-in and add Authorization with the value Bearer qrx_live_… under Request headers (where your organisation has request headers). Authentication can't be changed after saving; remove the connector and add it again.

Free Claude plans can add one custom connector.

ChatGPT

  1. Open chatgpt.com/plugins on the web, select +, then Add custom MCP server.
  2. Name: QRX. Server URL: https://qrx.codes/mcp.
  3. Authentication: OAuth. Accept the risk warning and select Create as a plugin.
  4. Sign in to QRX when ChatGPT asks.

ChatGPT's custom MCP servers don't take API keys. Workspace admins can restrict custom MCP servers on Business and Enterprise plans.

Cursor

Use the Install in Cursor button above, or add this to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{

"mcpServers": { "qrx": { "url": "https://qrx.codes/mcp" } } }

Cursor opens a browser to sign in to QRX when it connects.

With an API key instead:

{

"mcpServers": { "qrx": { "url": "https://qrx.codes/mcp", "headers": { "Authorization": "Bearer ${env:QRX_API_KEY}" } } } }

VS Code (GitHub Copilot)

Use the Install in VS Code button above, or add this to .vscode/mcp.json:

{

"servers": { "qrx": { "type": "http", "url": "https://qrx.codes/mcp" } } }

From a terminal:

code --add-mcp '{"name":"qrx","type":"http","url":"https://qrx.codes/mcp"}'

VS Code opens a browser to sign in to QRX when it connects.

With an API key instead (VS Code asks for it and stores it securely):

{

"inputs": [ { "type": "promptString", "id": "qrx-api-key", "description": "QRX API key (starts with qrx_)", "password": true } ], "servers": { "qrx": { "type": "http", "url": "https://qrx.codes/mcp", "headers": { "Authorization": "Bearer ${input:qrx-api-key}" } } } }

Windsurf / Devin Desktop

Edit mcp_config.json (macOS/Linux ~/.config/devin/mcp_config.json, Windows %APPDATA%\devin\mcp_config.json; older Windsurf installs use ~/.codeium/windsurf/mcp_config.json):

{

"mcpServers": { "qrx": { "serverUrl": "https://qrx.codes/mcp" } } }

Note the key is serverUrl, not url. Windsurf asks you to sign in to QRX when it connects. With an API key instead, add "headers": { "Authorization": "Bearer ${env:QRX_API_KEY}" }.

Cline

Open MCP Servers → Configure MCP Servers and add to cline_mcp_settings.json:

{

"mcpServers": { "qrx": { "type": "streamableHttp", "url": "https://qrx.codes/mcp", "disabled": false, "autoApprove": ["list_styles", "get_qr_code", "list_qr_codes", "get_account", "get_profile"] } } }

Cline asks you to sign in to QRX when it connects. In the Cline CLI, run cline mcp, choose qrx and Authorize OAuth. With an API key instead, add "headers": { "Authorization": "Bearer qrx_live_…" }.

Zed

Add to settings.json:

{

"context_servers": { "qrx": { "url": "https://qrx.codes/mcp" } } }

Zed asks you to sign in to QRX when it connects. With an API key instead, add "headers": { "Authorization": "Bearer qrx_live_…" }; Zed then skips sign-in.

Goose

Run goose configure → Add Extension → Remote Extension (Streamable HTTP) and enter https://qrx.codes/mcp. Or edit config.yaml (macOS/Linux ~/.config/goose/config.yaml, Windows %APPDATA%\Block\goose\config\config.yaml):

extensions:

qrx: name: qrx type: streamable_http enabled: true uri: https://qrx.codes/mcp timeout: 300

Goose opens your browser to sign in to QRX when it connects. With an API key instead, add the header Authorization: Bearer qrx_live_… (headers: in config.yaml).

OpenAI Codex CLI

codex mcp add qrx --url https://qrx.codes/mcp

Codex finds QRX's sign-in and opens your browser. Run codex mcp login qrx to sign in again later. The entry in ~/.codex/config.toml is just:

[mcp_servers.qrx]

url = "https://qrx.codes/mcp"

With an API key instead, add bearer_token_env_var = "QRX_API_KEY" to that entry.

Gemini CLI

gemini mcp add --transport http -s user qrx https://qrx.codes/mcp

Gemini CLI opens your browser to sign in to QRX when it connects; /mcp auth qrx signs in again later. Or in ~/.gemini/settings.json (note httpUrl, which selects Streamable HTTP):

{

"mcpServers": { "qrx": { "httpUrl": "https://qrx.codes/mcp" } } }

With an API key instead:

gemini mcp add --transport http -s user --header "Authorization: Bearer $QRX_API_KEY" qrx https://qrx.codes/mcp

LM Studio

In the Program tab, choose Install → Edit mcp.json and add:

{

"mcpServers": { "qrx": { "url": "https://qrx.codes/mcp" } } }

LM Studio asks you to sign in to QRX when it connects. With an API key instead, add "headers": { "Authorization": "Bearer qrx_live_…" }.

Agent Skills (any compatible agen

Only the beginning is shown; read the rest in the repo

Ask PopNx