Bring Ticketing
to CrewAI
Learn how to connect Smeetz to CrewAI and start using 6 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Smeetz MCP Server?
Connect your Smeetz account to any AI agent to streamline your booking and commerce workflows through natural conversation.
What you can do
- Product Catalog — List all available products in your account and fetch detailed metadata for specific items using their unique IDs.
- Booking Management — Create new bookings for specific products and dates, including ticket details and customer information, or retrieve existing booking statuses.
- Customer Insights — Access your full customer list and retrieve detailed profiles to provide personalized service or analyze buyer behavior.
- Real-time Queries — Get instant information on product availability and booking details without leaving your AI interface.
How it works
- Subscribe to this server
- Enter your Smeetz API Key
- Start managing your commerce operations from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Operations Managers — quickly check product details and booking statuses without navigating the Smeetz dashboard.
- Customer Support Teams — retrieve customer profiles and booking information instantly to resolve inquiries faster.
- Sales Teams — create bookings on the fly during customer interactions.
Built-in capabilities (6)
Requires product ID, date, ticket details, and customer information. Create a new booking for a specific product and date
Get detailed information about a specific booking
Get detailed information about a specific customer
Get detailed information about a specific product
List all customers
List all products available in your account
Why CrewAI?
When paired with CrewAI, Smeetz becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Smeetz 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
Smeetz in CrewAI
Smeetz and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Smeetz 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 | 4,000+ 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 Smeetz in CrewAI
The Smeetz 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 6 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
Smeetz for CrewAI
Every tool call from CrewAI to the Smeetz MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I retrieve full metadata for a specific product?
Yes, use the get_product tool with the product ID to get all technical and commercial details associated with that item.
Is it possible to automate new bookings through the AI?
Absolutely. The create_booking tool allows you to specify the product, date, ticket types, and customer information to generate a booking instantly.
How can I access customer information?
You can use list_customers to browse your customer database or get_customer with a specific ID to see a detailed profile and history.
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.
Explore More MCP Servers
View all →
NeverBounce
10 toolsVerify and clean email addresses via NeverBounce — track single checks and bulk jobs directly from your AI agent.
Helius (Solana)
14 toolsAccess high-performance Solana data—fetch assets, balances, transaction history, and priority fee estimates directly through your AI agent.
Scaleway
3 toolsManage Scaleway cloud infrastructure — list, create, and control virtual instances directly from your AI agent.
LangSmith (LLM Observability & Hub)
6 toolsMonitor LLM apps via LangSmith — track traces, audit prompt templates, and manage evaluation datasets.