Bring Data Exploration
to CrewAI
Learn how to connect Omni BI Intelligence to CrewAI and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for Subscribers
What is the Omni BI Intelligence MCP Server?
Connect your Omni BI (omni.co) account to your AI agent and gain deep insights into your organization's data through natural conversation and programmatic query execution.
What you can do
- Dashboard Oversight — List all available BI dashboards and retrieve detailed layout and component metadata.
- Data Model Intelligence — Access the semantic layer to list models and inspect specific field definitions and logic.
- Programmatic Queries — Execute custom queries against your data models directly from the chat and view results.
- Resource Management — Browse workspaces, folders, and projects to stay organized within your BI instance.
- Connection Monitoring — List all connected databases and data sources integrated with Omni.
- Data Export — Generate temporary export links for query results in CSV, JSON, or Excel formats.
- Deep Inspection — Fetch complete metadata for specific fields, dashboards, or data models using their unique IDs.
How it works
1. Subscribe to this server
2. Enter your Omni BI Instance URL and API Key (Bearer Token)
3. Start exploring your business intelligence from Claude, Cursor, or any MCP client
Who is this for?
- Data Analysts — quickly check model field logic or run ad-hoc queries without opening the UI.
- Business Leads — monitor key dashboard metrics and organization workspaces through natural language.
- Operations Teams — automate the retrieval of data exports and model metadata for reporting.
Built-in capabilities (10)
Export data to file
Get specific dashboard info
Get specific field info
Get data model metadata
List organization workspaces
List BI dashboards
List database connections
List Omni data models
List dashboard folders
Run programmatic query
Why CrewAI?
When paired with CrewAI, Omni BI Intelligence becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Omni BI Intelligence 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
Omni BI Intelligence in CrewAI
Omni BI Intelligence and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Omni BI Intelligence 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 Omni BI Intelligence in CrewAI
The Omni BI Intelligence 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 10 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
Omni BI Intelligence for CrewAI
Every tool call from CrewAI to the Omni BI Intelligence MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I get an Omni BI API Key?
Log in to your Omni instance, navigate to user settings or organization settings, and look for the API Tokens section to generate a new token.
Can I run raw SQL queries?
This implementation uses the run_omni_query tool which interacts with your defined data models (semantic layer). Raw SQL access depends on your specific model configuration in Omni.
What formats are supported for data export?
The export_query_results tool supports CSV, JSON, and XLSX formats. You will receive a temporary URL to download the requested file.
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.