Qr Agent Core MCP Server

QR-as-a-Service infrastructure for AI agents — generate, manage, and track QR codes programmatically. The qr agent core mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

QR-as-a-Service API built for AI agents. Create, update, and track dynamic QR codes programmatically via REST API or MCP (37 tools).

• Dynamic QR codes — — change the destination URL without regenerating the image
• 11 QR types — — URL, vCard, WiFi, Email, SMS, Phone, Event, Text, Location, Social, App Store
• Custom styling — — dot shapes (square, rounded, dots, classy-rounded), corner styles, colors, gradients, logo embedding, frames with CTA text
• SVG & PNG — — vector and bitmap output
• Enriched analytics — — device type, browser, OS, country, city, referrer, scans-by-day
• Real-time webhooks — — HMAC-SHA256 signed payloads with delivery logging

Its toolset

Everything the assistant can do here goes through one of these:

• Method — Path
• POST — /api/qr
• GET — /api/qr
• PATCH — /api/qr/:shortId
• DELETE — /api/qr/:shortId
• PUT — /api/domain
• create_qr_code — Create a URL QR code with optional custom styling
• get_qr_code — Get QR code details by short ID
• update_qr_destination — Change where a QR code redirects
• list_qr_codes — List all QR codes with pagination
• delete_qr_code — Delete a QR code and its analytics
• get_qr_analytics — Get scan stats and breakdowns

Configuration

You will need 7 environment variables: API_KEY, BASE_URL, DATABASE_URL, ADMIN_SECRET, STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET, STRIPE_PRICE_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at qr-for-agent on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Qr Agent Core's toolset — Method, POST, GET and 11 more — is a fair guide to whether it matches your workflow. It is maintained by benswel; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Qr Agent Core.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the qr agent core mcp server does with a few real requests.