Q
quartzondev/qr-branding-mcp
MCP server for the QR Branding API.
updated 2026-11-13
View on GitHub ↗Direct link · no redirect page
We have no copy-paste install command and no public remote endpoint, so we do not print a config. The step above is reference only, not a command we can vouch for. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 0 ★ · quartzondev/qr-branding-mcp · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
quartzondev/qr-branding-mcp;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# QR Branding MCP server
Excerpted from the repository README (abridged)
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. |
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/quartzondev-qr-branding-mcp/)
- Source
- awesome · https://github.com/quartzondev/qr-branding-mcp
- Browse by field
- MCP servers
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.