Bring Qr Codes
to CrewAI
Learn how to connect Uniqode to CrewAI 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 CrewAI?
When paired with CrewAI, Uniqode becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Uniqode tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Uniqode in CrewAI
Uniqode and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Uniqode to CrewAI 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 CrewAI
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 CrewAI 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 CrewAI
Every tool call from CrewAI 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 CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.