Quality QR MCP Server
[Validate manifests]
[Smithery]
[MCP]
[Protocol]
[License]
Create and manage trackable QR codes through AI assistants like Claude, Cursor, and any MCP-compatible tool.
Unlike generic QR code generators, Quality QR codes are saved to your account with scan tracking, analytics, and the ability to update destinations without reprinting.
Endpoint: https://quality-qr.app/api/mcp
Setup
1. Get an API Key
Sign up at quality-qr.app and generate an API key at Dashboard > Settings > API Keys.
2. Configure Your MCP Client
Smithery users: If you install via Smithery, you'll be prompted for your apiKey directly — Smithery handles the Authorization header for you. The configs below are for manual setup.
Claude Desktop
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on Mac):
Cursor
Add to your Cursor MCP settings:
Claude Code
3. Start Using It
Ask your AI assistant:
- "Create a QR code for https://example.com"
- "Make a WiFi QR code for network MyWiFi with password guest123"
- "Show me the analytics for my QR codes"
- "List all my QR codes"
- "Disable QR code abc123"
Available Tools
QR Code Types
Dynamic (URL can be changed after printing): URL, PDF, Menu, App Store, Social
Static (data encoded directly): WiFi, vCard, Email, Phone, SMS, Text, Event
Rate Limits
MCP tool calls count against your API rate limit. Protocol messages (initialize, tools/list) are free.
Rate-Limit Response Headers
Every response includes headers to help you manage usage:
When you receive a 429 Too Many Requests response, wait for the number of seconds specified in Retry-After before retrying.
Security
- All requests authenticated via API key (Bearer token)
- Keys can be revoked instantly from the dashboard
- QR codes are scoped to your account (no cross-user access)
- No admin, billing, or team management operations exposed
- GDPR and CCPA compliant, hosted on Cloudflare's global edge network
- See SECURITY.md to report a vulnerability, and PRIVACY.md for data handling details
API Key Management
Your API key grants full access to your QR codes and analytics. Treat it like a password.
- Rotate regularly. Generate a new key in Dashboard > Settings > API Keys, update your MCP client config, then revoke the old key. You can have multiple active keys to allow zero-downtime rotation.
- Revoke compromised keys immediately. Revocation takes effect instantly — any in-flight requests using the old key will fail.
- Restrict access to config files. MCP client configs store your key in plaintext. On macOS/Linux, ensure only your user can read them (e.g.,
chmod 600). Avoid committing config files with real keys to version control.
Links
Protocol
This is a remote MCP server using Streamable HTTP transport (JSON-RPC 2.0 over HTTP POST). No local installation required. Compatible with MCP protocol version 2025-03-26.