Bring Data Exploration
to Cursor
Learn how to connect Omni BI Intelligence to Cursor and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
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 Cursor?
Cursor's Agent mode turns Omni BI Intelligence into an in-editor superpower. Ask Cursor to generate code using live data from Omni BI Intelligence and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Omni BI Intelligence in Cursor
Omni BI Intelligence and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Omni BI Intelligence to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
