QRX

What the QRX MCP server does

The QRX MCP server connects an MCP client to QRX’s hosted QR-code service. It turns a prompt describing an appearance and a link into an art QR code intended for posters, menus, packaging, and signage. QRX checks that the generated artwork decodes before returning it, then provides an image and a hosted short link in the form https://qrx.to/<id>.

The service also supports ongoing code management. You can create variations from an existing code without changing the original, inspect generation status, list account codes, and update the destination behind an existing printed code. Destination changes require a paid plan and replace the previous URL.

How it works

The remote endpoint is https://qrx.codes/mcp. It uses stateless Streamable HTTP, so the client connects directly rather than starting a local process. Authentication is required for every request. MCP clients that support OAuth 2.1 can sign in through the QRX authorization flow; scripts and clients without sign-in support can send a QRX API key as a bearer token.

Generation may still be in progress when a request begins. get_qr_code can wait for up to 25 seconds, with 25 seconds as the default, and returns the code’s status, image, and short link. QRX MCP server calls can therefore be used interactively while an agent waits for the artwork to finish.

Setup and configuration

Add the server URL to a compatible client and complete QRX account sign-in when prompted. For API-key authentication, create a key in the QRX developer settings and keep it in an environment variable such as QRX_API_KEY. Send it as Authorization: Bearer qrx_…; clients that cannot add the bearer prefix can use the X-API-Key header instead.

The repository documents setup for Claude Code, Claude Desktop, Cursor, VS Code with GitHub Copilot, Windsurf, and ChatGPT. Claude Code can also install the repository plugin, which adds a QRX skill and a code card display in supported terminal or desktop contexts. The MCP server itself remains available through the remote HTTP endpoint.

Tools and capabilities

• generate_qr_code: starts a code from a prompt and link and immediately returns its ID.
• vary_qr_code: creates a separate version with a visual change while retaining the same destination.
• get_qr_code: retrieves status, image, and short link, optionally waiting for completion.
• list_qr_codes: returns account codes newest first, with cursor-based pagination.
• change_qr_code_destination: replaces the absolute HTTP or HTTPS destination for an existing code on a paid plan.
• get_account and get_profile: show plan, daily allowance, reset timing, account capabilities, and the connected account.
• list_styles: returns styles accepted by the generation tool.

Limitations and notes

A QRX account and authentication are required. API keys should be treated as secrets and can be revoked from the QRX developer settings. Daily generation availability depends on the account plan. Changing a destination is marked destructive because the old destination is replaced, although the printed QR code continues to work through its hosted short link. QRX MCP server access is remote; the supplied material does not describe a local server implementation.