QRX
概览
作者提供的说明(英文原文)
Turn a prompt and a link into a branded, print-ready QR code that always scans.
PopNx MCP 的三大支柱
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
- 用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
- 我们的基础检查i3 项中通过 3 项依据公开信息检查;尚未扫描代码
- 使用情况i起步阶段↓ 60/周 · ★ –
它能帮你做什么
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
- 连接方式: 电脑或云端
- 传输方式: stdio, Streamable HTTP
- 分类: 搜索与 AI 记忆
- 你需要填写:QRX_API_KEY, Authorization
安装
选择你使用的 AI 应用,然后复制设置。
安装之前
- 基础检查:3 项中通过 3 项
- 在作者的服务器上运行:你向它提出的内容会经过他们的服务器。
- 需要你自己填写:
QRX_API_KEY,Authorization
标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
或者在你的电脑上运行
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"qrx": {
"command": "npx",
"args": [
"-y",
"@qrxcodes/mcp"
],
"env": {
"QRX_API_KEY": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add --transport http qrx https://qrx.codes/mcp --header 'Authorization: Bearer {qrx_api_key}'或者在你的电脑上运行
claude mcp add qrx --env QRX_API_KEY=your-value -- npx -y @qrxcodes/mcp运行前请先填写空着的值。
或者自己复制设置
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"qrx": {
"url": "https://qrx.codes/mcp",
"headers": {
"Authorization": "Bearer {qrx_api_key}"
}
}
}
}或者在你的电脑上运行
或者自己复制设置
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"qrx": {
"command": "npx",
"args": [
"-y",
"@qrxcodes/mcp"
],
"env": {
"QRX_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
或者自己复制设置
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"qrx": {
"type": "http",
"url": "https://qrx.codes/mcp",
"headers": {
"Authorization": "Bearer {qrx_api_key}"
}
}
}
}或者在你的电脑上运行
或者自己复制设置
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"qrx": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@qrxcodes/mcp"
],
"env": {
"QRX_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
需要你填写的值
- 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机密 HTTP headerOptional. 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.
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它能做什么
服务器要求先登录,才会列出它的工具。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月9日
- ✓ 通过
作者与仓库一致
注册名称已通过域名 qrx.codes 验证(注册中心会核实域名所有权)
- … 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
- … 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
- ✓ 通过
端点有响应
在 976 毫秒内响应(HTTP 401)
- ✓ 通过
使用 OAuth 登录
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
- … 尚未检查
工具描述中没有隐藏指令
尚未检查;我们会在检查端点时读取工具列表
与“搜索与 AI 记忆”中的其他服务器比较i
- 星标数多于此分类中其他 5744 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 5744 个服务器的 56% 更新
- 基础检查结果等于或优于此分类中其他 5744 个服务器的 100%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
QRX 安全吗?
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
你需要填写:QRX_API_KEY, Authorization
它在我的电脑上运行还是在云端?
两种方式都可以:安装在你的电脑上,或者连接云端版本。
它还在维护吗?
GitHub 仓库最后更新于–,最新版本(1.2.4)于30天前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
有什么可以替代它?
同一分类中有:Context7, Codebase Memory, Exa
替代选择
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Codebase Memory
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Exa
Connect AI agents to Exa for web search, content fetching, and multi-step research.
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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 URL | https://qrx.codes/mcp |
| Transport | Streamable HTTP (stateless) |
| Auth | Required 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 key | Authorization: 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 auth | Every 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 list | https://qrx.codes/.well-known/mcp/server-card.json |
| Docs | qrx.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:
- Sign in at qrx.codes (free).
- Open qrx.codes/developers/keys and create a key. It starts with
qrx_. - Keep it secret. The examples below read it from an environment variable called
QRX_API_KEYwherever 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.
- 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.
- Name:
QRX. URL:https://qrx.codes/mcp. - Authentication: Sign in now, then sign in to QRX when Claude asks.
- 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
- Open chatgpt.com/plugins on the web, select +, then Add custom MCP server.
- Name:
QRX. Server URL:https://qrx.codes/mcp. - Authentication: OAuth. Accept the risk warning and select Create as a plugin.
- 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
只显示了开头部分;其余内容请在仓库中阅读