Q
quartzondev/qr-branding-mcp
MCP server for the QR Branding API.
更新 2026-11-13
在 GitHub 查看 ↗直链 · 无中转页
我们没有可直接复制的安装命令,也没有公开的远端端点,所以不出配置。上面那条命令仅供参考,不是我们能担保的可复制命令——编一条出来比不给更糟。 各客户端的接法 →
- ★ 数取值
- 0 ★ · quartzondev/qr-branding-mcp · 取自 GitHub 搜索 API · (2026-11-19 20:00:48 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-11-18 · 最近见到 2026-11-20 · 共见到 3 次 · 被 3 个来源列出
- 评分构成
- 综合分 300 · 3 个来源 · mcp
常见问题(答案都来自我们的记录)
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
quartzondev/qr-branding-mcp;我们收录于 2026-11-18;最近见到 2026-11-20。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。README 原文(英文,未翻译) · 在 GitHub 读完整 README →
# QR Branding MCP server
以下摘录自该仓库的 README(片段)
MCP server for the QR Branding API. Lets Claude Desktop, Claude Code, Cursor, Cline, VS Code, ChatGPT desktop, and any other Model Context Protocol client generate branded QR codes, render any of the 118 curated templates, print-ready posters, or assemble Wi‑Fi / vCard / geo payloads — and check a design the way a phone camera will read it.
Every render is decoded server-side (ISO/IEC 18004) before it is returned, so a design that would not scan is caught here instead of on the printed piece.
npm: @qr-branding/mcp-server · version in server.json / package.json
Official MCP registry: io.github.quartzondev/qr-branding
Remote endpoint (no install): https://qr-branding.com/mcp
Docs (9 languages):
Agent-oriented install sheet: llms-install.md
## Install
bash
npx -y @qr-branding/mcp-server
The server starts without an API key: tools/list works, and any tool that needs the gateway explains how to get a key instead of failing silently. Read Limits and billing for what a key unlocks.
## Get an API key
Sign in at qr-branding.com and create a key under Dashboard → API keys (/dashboard/keys). Keys look like qrb_xxx.... API access requires an active Studio pack; without one every call returns HTTP 402 studio_required.
## Client config
### Claude Desktop (claude_desktop_config.json) / Claude Code (.mcp.json)
Claude Desktop: Settings → Developer → Edit Config opens the file (macOS ~/Library/Application Support/Claude/claude_desktop_config.json, Windows %APPDATA%\Claude\claude_desktop_config.json).
json
"mcpServers": {
"qr-branding": {
"command": "npx",
"args": ["-y", "@qr-branding/mcp-server"],
"env": {
"QR_BRANDING_API_KEY": "qrb_xxx"
Omit the env block to start in keyless mode.
### Cursor / Cline / VS Code
Same command + args + env shape as above, in the client's own MCP settings file (%USERPROFILE%\.cursor\mcp.json, Cline's MCP Servers → Configure, .vscode/mcp.json).
### Optional environment
QR_BRANDING_API_KEY — Studio key. Without it the tools that hit the gateway return a message explaining how to create one.
QR_BRANDING_API_BASE_URL — override the gateway URL. Default https://qr-branding.com. Useful for self-hosters and staging.
## Remote server (no install)
The same eleven tools are served over Streamable HTTP at https://qr-branding.com/mcp.
bash
claude mcp add --transport http qr-branding https://qr-branding.com/mcp --header "Authorization: Bearer qrb_xxx"
Without a key the remote server answers in a keyless trial mode: every tool except qr_generate_ai, PNG up to 720 px, 20 tool calls per day per network. A Studio key unlocks SVG/PDF, up to 4K, posters and AI designs.
Clients that prefer a browser consent flow over pasting a key can use the bundled OAuth 2.1 server (dynamic client registration + PKCE): the 401 on https://qr-branding.com/mcp carries WWW-Authenticate: Bearer resource_metadata="https://qr-branding.com/.well-known/oauth-protected-resource", so the client discovers the authorization server and walks the user through consent.
## Tools
| Tool | What it does |
| qr_generate | Manual QR generation with explicit colors, module/finder shapes, logo, caption, format. |
| qr_generate_ai | Prompt-driven design — the server-side LLM picks the style for you. |
Every render is decoded server-side (ISO/IEC 18004) before it is returned, so a design that would not scan is caught here instead of on the printed piece.
npm: @qr-branding/mcp-server · version in server.json / package.json
Official MCP registry: io.github.quartzondev/qr-branding
Remote endpoint (no install): https://qr-branding.com/mcp
Docs (9 languages):
Agent-oriented install sheet: llms-install.md
## Install
bash
npx -y @qr-branding/mcp-server
The server starts without an API key: tools/list works, and any tool that needs the gateway explains how to get a key instead of failing silently. Read Limits and billing for what a key unlocks.
## Get an API key
Sign in at qr-branding.com and create a key under Dashboard → API keys (/dashboard/keys). Keys look like qrb_xxx.... API access requires an active Studio pack; without one every call returns HTTP 402 studio_required.
## Client config
### Claude Desktop (claude_desktop_config.json) / Claude Code (.mcp.json)
Claude Desktop: Settings → Developer → Edit Config opens the file (macOS ~/Library/Application Support/Claude/claude_desktop_config.json, Windows %APPDATA%\Claude\claude_desktop_config.json).
json
"mcpServers": {
"qr-branding": {
"command": "npx",
"args": ["-y", "@qr-branding/mcp-server"],
"env": {
"QR_BRANDING_API_KEY": "qrb_xxx"
Omit the env block to start in keyless mode.
### Cursor / Cline / VS Code
Same command + args + env shape as above, in the client's own MCP settings file (%USERPROFILE%\.cursor\mcp.json, Cline's MCP Servers → Configure, .vscode/mcp.json).
### Optional environment
QR_BRANDING_API_KEY — Studio key. Without it the tools that hit the gateway return a message explaining how to create one.
QR_BRANDING_API_BASE_URL — override the gateway URL. Default https://qr-branding.com. Useful for self-hosters and staging.
## Remote server (no install)
The same eleven tools are served over Streamable HTTP at https://qr-branding.com/mcp.
bash
claude mcp add --transport http qr-branding https://qr-branding.com/mcp --header "Authorization: Bearer qrb_xxx"
Without a key the remote server answers in a keyless trial mode: every tool except qr_generate_ai, PNG up to 720 px, 20 tool calls per day per network. A Studio key unlocks SVG/PDF, up to 4K, posters and AI designs.
Clients that prefer a browser consent flow over pasting a key can use the bundled OAuth 2.1 server (dynamic client registration + PKCE): the 401 on https://qr-branding.com/mcp carries WWW-Authenticate: Bearer resource_metadata="https://qr-branding.com/.well-known/oauth-protected-resource", so the client discovers the authorization server and walks the user through consent.
## Tools
| Tool | What it does |
| qr_generate | Manual QR generation with explicit colors, module/finder shapes, logo, caption, format. |
| qr_generate_ai | Prompt-driven design — the server-side LLM picks the style for you. |
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/quartzondev-qr-branding-mcp/)
- 来源
- awesome · https://github.com/quartzondev/qr-branding-mcp
- 按领域浏览
- MCP 服务
- 收录来源
- 3 个独立来源
- 收录于
- 今天
更多 MCP 服务器
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。