logo
APIAutomations•

Connect CodeQR to Claude, ChatGPT and Cursor with MCP

Add the CodeQR MCP server to Claude, ChatGPT, Cursor, VS Code or Claude Code, sign in to pick a workspace, and let the assistant manage links and QR codes.

Avatar for undefined
CodeQR Team
Equipe de Conteúdo

The CodeQR MCP server lets an AI assistant do what you do in the dashboard — create a short link on your domain, generate a dynamic QR code, change where a printed code points, list what it created, read scans and clicks — from a chat. This guide connects the three most common clients, explains the sign-in, and sets expectations about what the assistant can and cannot do.

Availability

  • Plan: every plan. The assistant works inside one workspace with the permissions of the person who signed in; created links and codes count against that workspace's quotas.
  • Where: server URL https://mcp.codeqr.io/mcp (Streamable HTTP). It appears as CodeQR MCP in Settings → Integrations once a workspace is connected; the card reads Access is granted per project, and can be revoked at any time from Settings → Integrations. Reference: MCP on docs.codeqr.io.

Before you start

  • No API key is needed or accepted. The first request opens your browser, you sign in to CodeQR and pick the workspace to grant; the client stores the token from then on.
  • One signed-in client at a time per workspace: signing in from a second client — or re-authorizing the same one — replaces the previous authorization for that workspace.
  • The assistant cannot record or read conversion events (leads, sales); link and QR objects still show their clicks, leads and sales counters.
  • Clients ask for confirmation before tools that publish or rewrite something (create, update, delete). Keep that on.

Steps

  1. Claude (web or desktop app): open Customize → Connectors, click + → Add custom connector, paste https://mcp.codeqr.io/mcp, leave the OAuth fields under Advanced settings empty and save. On first use Claude opens the CodeQR sign-in; choose the workspace and allow.
  2. ChatGPT: Settings → Advanced → Developer Mode, then the Connectors tab → Add Connector, enter https://mcp.codeqr.io/mcp. ChatGPT discovers the OAuth endpoints and prompts you to authorize.
  3. Cursor: add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project):
{ "mcpServers": { "codeqr": { "url": "https://mcp.codeqr.io/mcp" } } }
  1. VS Code: .vscode/mcp.json:
{ "servers": { "codeqr": { "type": "http", "url": "https://mcp.codeqr.io/mcp" } } }
  1. Claude Code (terminal):
claude mcp add --transport http codeqr https://mcp.codeqr.io/mcp
  1. Ask the assistant to list the CodeQR tools. You should see fourteen: create_link, list_links, get_link_info, update_link, delete_link, create_qrcode, list_qrcodes, update_qrcode, delete_qrcode, get_analytics, list_domains, list_tags, create_tag, get_workspace.

What to ask for

  • "Create a short link on go.example.com for https://example.com/spring-menu, key spring-menu, tag menu." → create_link, returns the short link.
  • "Make a dynamic QR code for our Wi-Fi network CafeGuest with password **, title Counter Wi-Fi." → create_qrcode (types: url, text, email, phone, sms, wifi, vcard, crypto, whatsapp).
  • "The QR code on the tables should now open https://example.com/summer-menu — update it, do not create a new one." → update_qrcode; the printed code keeps working.
  • "How many scans did the tables' QR code get this week, by country?" → get_analytics with event: scans, groupBy: countries, interval: 7d.
  • "Which workspace and plan am I connected to?" → get_workspace ({ "id", "slug", "name", "plan" }) — ask this first when you have several workspaces.

The server tells the model that every link and code is a live endpoint whose destination stays editable after printing and whose scans are recorded, and that changing a link's key breaks copies already shared. Expect the assistant to prefer update_link/update_qrcode over recreating.

Revoke or switch workspace

Open Settings → Integrations → CodeQR MCP and uninstall it (⋮ → Uninstall Integration), or sign in again from the client and pick another workspace — the newer authorization replaces the older one.

Verify it works

  1. Ask for the tool list (step 6). Fourteen tools means the connection is complete — a "connected" badge alone is not proof.
  2. Ask the assistant to create one test link. It appears in Links in the dashboard within seconds; Settings → Integrations shows CodeQR MCP as enabled with your name under INSTALLED BY.
  3. Ask it to delete that test link.

Troubleshooting

The client says connected but the assistant has no CodeQR tools

The OAuth step did not finish, or the client cached an old session. Remove the connector, add it again and complete the browser sign-in; then ask for the tool list.

The assistant works in the wrong workspace

The token belongs to the workspace picked at sign-in. Re-authorize and choose the right one — the previous authorization is replaced. get_workspace tells you which one is active.

My colleague lost access when I connected

One client per workspace: your sign-in replaced theirs. Each person can connect a different workspace, or one person keeps the connection.

"list_domains" returns an error page

At the time of writing this tool answers with a not-found page instead of your domains. Ask for the domain in the dashboard's Domains page, or pass the domain explicitly in create_link.

The assistant refuses to record a lead or sale

Conversion tracking is not exposed through MCP. Use the API (POST /track/lead, POST /track/sale) or the SDK.

Related articles