QR-hi for AI assistants (MCP)

Connect QR-hi to an AI assistant and manage your codes in plain words: create a code for the new menu, point a printed poster at this month’s page, ask which code got the most scans by country. Everything happens in your own QR-hi account, under your own plan, and shows up in the dashboard like anything you make by hand.

The connector speaks the Model Context Protocol (MCP), the open standard assistants use to call outside tools. It is not tied to one assistant: Claude, ChatGPT, Cursor and any other client that supports MCP connectors with OAuth sign-in connect to the same address.

Connector address: https://api.qr-hi.com/functions/v1/mcp

Claude

1. In Claude, open Settings, then Connectors, and choose Add custom connector.
2. Paste the connector address. Leave the OAuth fields empty; the server registers the client itself.
3. Press Connect. QR-hi opens its consent page; sign in if asked, read what the connector will be able to do, and press Allow.

Once the connector is listed in the Claude directory you can also add it from there with one click.

Claude Code

In the terminal:

claude mcp add --transport http qr-hi https://api.qr-hi.com/functions/v1/mcp

Then run /mcp, pick qr-hi and choose Authenticate. The browser opens the same consent page.

ChatGPT

Add a connector in ChatGPT’s settings, give it the connector address and choose OAuth as the sign-in method. ChatGPT sends you to the QR-hi consent page; press Allow and the tools appear in the conversation.

Cursor

Add the server to ~/.cursor/mcp.json (or the project’s .cursor/mcp.json):

{ "mcpServers": { "qr-hi": { "url": "https://api.qr-hi.com/functions/v1/mcp" } } }

Cursor shows a sign-in prompt for the server; it leads to the same consent page.

Other assistants and your own code

Any MCP client that supports streamable HTTP and OAuth sign-in works the same way: give it the address, approve the consent page once. If you write your own client, send a QR-hi session token in the Authorization: Bearer header; the server answers an unauthenticated call with a 401 that points at its OAuth metadata.

What you can ask

• “Make a QR code for our autumn menu at example.com/menu and call it Autumn menu”
• “Point the lobby poster’s code at the October events page”
• “Which of my codes got the most scans this month, and from which countries?”
• “Pause the code called Summer promo”
• “Make 40 codes, one per table, pointing at example.com/order?table=1 through 40”
• “Show me the QR image for the business card code”

Assistants that honour tool annotations, such as Claude, ask before they create, change or delete anything; reading needs no confirmation.

What the connector can do

Tool	What it does
get_account	Your plan, how many codes you have, storage and history limits
list_code_types	Which kinds of codes can be made here
list_qr_codes	Find codes by name, address, kind, type or status
get_qr_code	One code with its scan link and dashboard link
create_qr_code	A QR code or short link for a web address, or a text QR code
update_qr_code	Rename, re-point a link code, pause or resume it
delete_qr_code	Delete a code for good; marked destructive so assistants ask first
get_scan_stats	Totals, unique visitors, daily series, device, browser, country and city
bulk_create_qr_codes	Many link codes in one batch
get_qr_image	The QR as SVG in your saved design

Codes that need a file, such as PDF, image and contact card codes, are made in the dashboard. The connector can still list them and read their statistics.

Limits and safety

The connector follows the same rules as the website. Your plan’s limits on codes, batches and history apply unchanged. Every web address goes through the same safety check as in the dashboard, so a dangerous link is refused in the assistant the way it is refused on the site. A code stopped by moderation cannot be changed through the connector.

Your data

The connector acts as you, through a sign-in you approve. It can read and change the codes and statistics in your account and nothing else: not your password, email or billing. QR-hi does not receive your conversation with the assistant, only the requests the tools make. Details are in the privacy policy.

Disconnect

Remove the connector in the assistant’s settings; the access it held stops working with it. You can connect again at any time.

Help

Write to [email protected] if something does not work as described.