Turn a prompt and a link into a branded, print-ready QR code that always scans.
Connect Remote server
claude mcp add --transport http mcp https://qrx.codes/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"mcp": {
"url": "https://qrx.codes/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"mcp": {
"type": "http",
"url": "https://qrx.codes/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://qrx.codes/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server asks for a key before it lists its tools. Connect it with your own key to see them.
Headers
| Name | Description |
|---|---|
AuthorizationOptional, secret | Optional. 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. |
Details
| Endpoint | https://qrx.codes/mcp (Streamable HTTP) |
| Package | @qrxcodes/[email protected] (NPM, stdio) |
| First published | 9 Oct 2026 |
| Last updated | 9 Oct 2026 |
| Registry name | codes.qrx/mcp |
More developer tools servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
