Bring Qr Codes
to Cline
Learn how to connect Uniqode to Cline and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Uniqode MCP Server?
Connect your Uniqode (formerly Beaconstac) account to any AI agent and simplify how you create, manage, and analyze your QR code campaigns through natural conversation.
What you can do
- QR Code Generation — Create dynamic or static QR codes for websites, vCards, or social media with full branding control.
- Scan Analytics — Retrieve detailed scan metrics by time, location (country/city), and device type to measure campaign performance.
- Dynamic Updates — Update the destination URL of your dynamic QR codes instantly without changing the physical code.
- Organization Oversight — List and manage QR codes across different organizations, folders, and campaigns.
- Lifecycle Management — Tag, categorize, and delete QR codes to keep your marketing dashboard organized.
- Account Visibility — Fetch account details and organization structures directly from the agent.
How it works
1. Subscribe to this server
2. Enter your Uniqode API Key (found in your account settings)
3. Start managing your QR code ecosystem from Claude, Cursor, or any MCP client
Who is this for?
- Marketing Managers — quickly update campaign destinations and check scan analytics via simple AI queries.
- Operations Teams — automate the creation of vCard QR codes for staff and manage organizational folders.
- Business Owners — monitor customer engagement and physical-to-digital attribution directly from the workspace.
Built-in capabilities (12)
qr_type: 1 for Website, 2 for vCard, etc. Create a new QR code
Delete a QR code
Get account details
Get scan analytics by location
Get scan analytics by time
Get QR code details
List campaigns
List folders
List organizations
List all QR codes
List tags
Update an existing QR code
Why Cline?
Cline operates autonomously inside VS Code. it reads your codebase, plans a strategy, and executes multi-step tasks including Uniqode tool calls without waiting for prompts between steps. Connect 12 tools through Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.
- —
Cline operates autonomously. it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts
- —
Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window
- —
Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation
- —
Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing
Uniqode in Cline
Uniqode and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Uniqode to Cline through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Uniqode in Cline
The Uniqode MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cline only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Uniqode for Cline
Every tool call from Cline to the Uniqode MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I change the URL of a QR code after it has been printed?
Yes, if it is a dynamic QR code. Use the update_qrcode tool and provide the new destination URL. The physical code remains the same but the user will be redirected to the new link.
How do I see where people are scanning my codes from?
Run the get_analytics_location query with your QR Code ID. It returns scan data aggregated by country and city, allowing you to track geographic engagement.
Is it possible to list all the tags I'm using for organization?
Absolutely. Use the list_tags query. The agent will retrieve all tags used for categorization, helping you filter and find specific QR codes more easily.
How does Cline connect to MCP servers?
Cline reads MCP server configurations from its settings panel in VS Code. Add the server URL and Cline discovers all available tools on initialization.
Can Cline run MCP tools without approval?
By default, Cline asks for confirmation before executing tool calls. You can configure auto-approval rules for trusted servers in the settings.
Does Cline support multiple MCP servers at once?
Yes. Configure as many servers as needed. Cline can use tools from different servers within the same autonomous task execution.
Server shows error in sidebar
Click the server name to see logs. Verify the URL and token are correct.