CrewAIFramework

Cube.dev MCP Server

Bring Semantic Layer
to CrewAI

Name: Cube.dev MCP Server
Price: 29 USD
Availability: InStock
Rating: 0.2 (1 reviews)
Author: Vinkius

Learn how to connect Cube.dev to CrewAI and start using 15 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

GDPR Free for Subscribers

Check LiveCheck ReadyConvert QueryExecute Cube SqlGenerate Meta TokenGet EntityGet MetaGet Pre Aggregation Job StatusGet SqlList Data SourcesList DeploymentsList EntitiesList EnvironmentsLoad QueryTrigger Pre Aggregation Job

Unlock for AI Agents

Ask AI about this MCP Server ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

What is the Cube.dev MCP Server?

Connect your Cube.dev instance to any AI agent to bridge the gap between natural language and your data warehouse. This server allows your agent to interact with Cube's semantic layer, ensuring consistent metrics and high-performance data retrieval.

What you can do

Data Querying — Execute complex REST API queries using load_query to fetch aggregated data with measures, dimensions, and filters.
SQL Inspection — Use get_sql and execute_cube_sql to debug or run raw queries against the SQL API for deep data investigation.
Metadata Exploration — Retrieve cube definitions, views, and segments via get_meta to understand your data model without leaving the chat.
Performance Management — Trigger and monitor background pre-aggregation builds with trigger_pre_aggregation_job to ensure your dashboards stay fast.
Cloud Management — List deployments and environments if using Cube Cloud to manage your infrastructure context.

How it works

Subscribe to this server
Provide your Cube API URL and Secret Token
Start asking questions about your data metrics and model structure

Who is this for?

Data Engineers — quickly verify data models and trigger cache refreshes via CLI or AI interface.
Analytics Engineers — debug generated SQL and inspect metadata to ensure metric consistency.
Product Managers — get instant answers to data questions by letting the AI query the semantic layer directly.

Built-in capabilities (15)

check_live

Check if Cube deployment is live

check_ready

Check if Cube deployment is ready

convert_query

Convert a SQL query to a REST API query format

execute_cube_sql

Execute a raw SQL query against the SQL API

generate_meta_token

Requires CUBE_CLOUD_API_KEY. Generate a JWT for the Metadata API

get_entity

Get detailed metadata for a specific entity

get_meta

Get metadata for cubes and views

get_pre_aggregation_job_status

Get status of pre-aggregation jobs

get_sql

Useful for debugging. Get generated SQL for a Cube query

list_data_sources

List configured data sources

list_deployments

Requires CUBE_CLOUD_API_KEY. List all Cube Cloud deployments

list_entities

List all cubes and views

list_environments

Requires CUBE_CLOUD_API_KEY. List environments for a deployment

load_query

Use this to get aggregated data. Execute a Cube query and return results

trigger_pre_aggregation_job

Trigger a pre-aggregation build job

Why CrewAI?

When paired with CrewAI, Cube.dev becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Cube.dev 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 mcps parameter 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

See it in action

Cube.dev in CrewAI

AI Agent→Vinkius

High Security·Kill Switch·Plug and Play

Why Vinkius

Cube.dev and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Cube.dev 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.

4,000+MCP Servers ready

<40msCold start

60%Token savings

	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

Unlock for AI Agents View step-by-step setup guide for CrewAI →

Enterprise Security

Why teams choose Vinkius for Cube.dev in CrewAI

The Cube.dev 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 15 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.

Unlock for AI Agents View full Cube.dev details →

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

The Vinkius Advantage

How Vinkius secures
Cube.dev for CrewAI

Every tool call from CrewAI to the Cube.dev MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start

Ed25519Signed audit chain

60%Token savings

FAQ

Frequently asked questions

Can I see the exact SQL that Cube generates for a specific query?

Yes. You can use the get_sql tool. By providing the query JSON, the agent will return the generated SQL string, which is perfect for debugging or verifying your data logic.

How do I refresh the data cache or pre-aggregations using the AI?

You can use the trigger_pre_aggregation_job tool. You can specify which cubes or data sources to target, and the agent will initiate the background build process for you.

Is it possible to explore the available measures and dimensions?

Absolutely. Use the get_meta tool to fetch all metadata. This allows the AI to understand what data is available to be queried, including views and segments.

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.