Your QR codes, from inside your AI assistant
A Model Context Protocol server that lets an assistant like Claude list your codes, read their analytics, check a UPI QR and repoint a printed code — using your own API key, with the same limits as the API.
From Pro · with an API keyEarly accessAsk for early access Read the API referencelist_qr_codesupdate_destinationget_analyticsDone — the Andheri table tent now opens the Diwali menu. The printed code is unchanged, and last week's scans are in your analytics.An illustration of a conversation. Any numbers an assistant reports come from your own account.12 tools, each a thin forward to an API endpoint you already have
Your codes
list_qr_codesList QR codes in the workspace this API key belongs to. · GET /v1/qrget_qr_codeFetch one QR code by id, including its design and payload. · GET /v1/qr/{id}create_qr_codeCreate a QR code that opens a URL — this tool makes URL codes only. · POST /v1/qrupdate_destinationRepoint a dynamic QR code to a new URL. · POST /v1/qr/{id}/destinationget_destination_historyThe append-only destination version history of a QR code, newest first. · GET /v1/qr/{id}/history
Measurement
get_usageThis workspace's usage against its plan limits — codes, scans, and what is left of each. · GET /v1/usageget_analyticsScan analytics for one QR code over the last N days (default 30): scans and unique visitors with the previous window for comparison, lifetime scans, a daily series, hours of the day in UTC, and breakdowns by place (country, region, city) and device (type, OS, browser). · GET /v1/qr/{id}/analytics
Bulk and pages
list_bulk_jobsList bulk jobs in this workspace, newest first, with row counts and progress. · GET /v1/bulkget_bulk_job_statusProgress of one bulk job: status, rows total, processed and failed, and when it started and finished. · GET /v1/bulk/{id}list_landing_pagesList the hosted landing pages in this workspace: title, slug, status (draft, published or scheduled) and when each was last published. · GET /v1/pages
Checks and files
render_qrRender a web address (http/https) or plain text as a QR code SVG. · POST /v1/rendervalidate_payment_qrCheck a UPI payment payload against the five-wallet compatibility engine (Google Pay, PhonePe, Paytm, BHIM, Amazon Pay) BEFORE printing. · POST /v1/payment/validate
On your machine, with your key
- Your assistant calls a toolClaude Desktop, or any client that speaks MCP over stdio.
- The server forwards itTo api.qrcodegenerator.in, with your API key as the bearer token.
- The API answers as it always doesSame scope, same limits and the same envelope as calling it yourself.
Early access. The server package is not published yet. Customers on Pro and up can ask us for it; this page will carry the install line when it is public.
No separate business logic, no shortcuts
- Your key, your scopeA tool can do exactly what your key can do — bulk tools need a key with the bulk scope.
- AI never writes a payloadThe assistant can propose a destination; what a code encodes is set by you and checked by the API.
- Printed codes keep resolvingRepointing changes where a code goes, never whether it works.
- No scores inventedScanability results report measured checks, the same as everywhere else.
API calls a month, shared with the API itself
- Pro
- 50,000
- Business
- 5,00,000
- Growth
- 10,00,000
- Agency
- 20,00,000
- Scale
- 50,00,000
Plans below Pro have no API access, so no MCP. A short per-key window also applies; going over it returns 429 with the limit in the response headers.