What is MCP, in plain words?
MCP stands for Model Context Protocol. It is an open standard, introduced by Anthropic in late 2024 and since adopted by OpenAI and others, that gives an AI assistant a safe way to use outside tools. Think of it as a USB port for AI: any app that has the port can plug in any tool that fits it.
QRBold is one of those tools. Our MCP server tells the assistant what it can do (“create a QR code”, “look up scan statistics”) and does the actual work when the assistant asks. You never see any of that — you just see the answer in the chat and the result in your dashboard.
Why connect an AI assistant to QRBold?
Most QR codes and digital business cards are made while you are doing something else: writing a campaign brief, preparing for an event, replying to a new contact. Opening a dashboard, filling a form and downloading a file breaks that flow. With the assistant connected, you describe what you need where you already are and the code or card appears in the same chat.
It also makes the numbers easier to get at. “Which of my codes got the most scans this month?” is a one-line question to an assistant and a five-click journey in most dashboards.
- Dynamic by default. Every QR code the assistant creates can be edited later, so a wrong link is a two-second fix rather than a reprint.
- Same account, same limits. The assistant uses your plan exactly as the dashboard does. Nothing bypasses your limits and everything shows up in your dashboard immediately.
- Every action is logged. The server records which app did what and when, so an admin can always answer “who created this?”
Sign in, or use an API key?
If you are a person using Claude, ChatGPT, Cursor or VS Code, sign in. It is faster, there is nothing to copy, and you can revoke it from a list. If you are running something unattended — a script, a CI job, an internal agent that has no browser — create an API key under Settings → Developer API and send it as a bearer token to the same URL. Both routes give the assistant the same tools.