Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Turn a prompt and a link into a branded, print-ready QR code that always scans.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
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 保存在这台设备上,无需账户。
Authorization 机密 HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 qrx.codes 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:QRX_API_KEY, Authorization
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(1.2.4)于28天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, FlyDocs
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.
| 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) |
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:
qrx_.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.
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.
QRX. URL: https://qrx.codes/mcp.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
QRX. Server URL: https://qrx.codes/mcp.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
只显示了开头部分;其余内容请在仓库中阅读