MCP server - Cube — ContextQMD

Cube MCP (Model Context Protocol) lets MCP-compatible AI clients connect to Cube over HTTPS using OAuth. You don’t need to run a local MCP server or manage API keys.

<Info>

The MCP server is available on Premium and Enterprise plans. Users need the Viewer role or higher to interact with the MCP server.

</Info>

What is MCP?

Model Context Protocol (MCP) is an open standard that enables AI assistants to securely connect to external data sources and tools. The Cube MCP Server acts as a bridge between your AI assistant and Cube's analytics platform, allowing you to ask data questions directly from your coding environment.

Remote MCP server (recommended)

Cube hosts a remote MCP server endpoint for your tenant. MCP clients connect over HTTPS and authenticate via OAuth.

Overview

Endpoint: https://<cube-mcp-server-host>/api/mcp
OAuth discovery: https://<cube-mcp-server-host>/.well-known/oauth
OAuth flow: Authorization Code + PKCE, client_id = cube-mcp-client, scope = mcp-agent-access
Agent selection: Uses the Remote MCP Defaults (default deployment + agent) set by your admin

Admin setup

Prerequisites

Before enabling Remote MCP, make sure you have:

Admin privileges in your Cube instance
An active Cube tenant
Remote MCP URL configured

1) Confirm Remote MCP URL

Remote MCP uses your Cube MCP server host. If the URL isn’t configured, the Remote MCP page will show “Remote MCP configuration is unavailable.”

2) Set Remote MCP Defaults

Go to Admin → Remote MCP and select:

Default Deployment
Default Agent

These defaults are required for the OAuth token exchange.

Connect to Claude

Claude Code

bash

claude mcp add --transport http cube-mcp-server https://<cube-mcp-server-host>/api/mcp

Authentication and usage flow:

Run the command copied from Admin → Remote MCP → Claude → Claude Code.
Then run Claude and use /mcp to list available servers.
Select cube-mcp-server and choose Authenticate.
A browser window opens for authentication.
Log into Cube and choose your tenant.
Return to Claude Code and start asking questions.

Claude (Team/Enterprise)

Open Settings in Claude (web or desktop).
Scroll to Integrations and click Add more.
Use:
- Integration name: Cube MCP
- Integration URL: https://<cube-mcp-server-host>/api/mcp
Complete the OAuth flow to grant access.
Enable tools in any new chats.

Use Cube in Claude chat

Start a new chat in Claude.
Open the tools menu and enable Cube MCP (use the tools search if you have many tools).
Ask a data question. Toggle the tool off to disable it for that chat.

Claude (Desktop app)

json

{
  "mcpServers": {
    "cube-mcp-server": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "--transport", "http", "https://<cube-mcp-server-host>/api/mcp"]
    }
  }
}

Connect to Cursor

Add the Remote MCP endpoint under Tools & MCP Settings, then complete the OAuth flow.

json

{
  "mcpServers": {
    "cube-mcp-server": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "--transport", "http", "https://<cube-mcp-server-host>/api/mcp"]
    }
  }
}

Connect to Codex

Preferred (CLI):

bash

codex mcp add cube-mcp-server --url https://<cube-mcp-server-host>/api/mcp

If this is your first time using MCP in Codex, enable the feature in ~/.codex/config.toml:

editorconfig

[features]
rmcp_client = true

Manual setup:

editorconfig

[features]
rmcp_client = true

[mcp_servers."cube-mcp-server"]
url = "https://<cube-mcp-server-host>/api/mcp"

Then run codex mcp login cube-mcp-server to authenticate.

Connect to other MCP clients

For any MCP-compatible client:

Add a new server with the Remote MCP Endpoint.
The client will auto-discover OAuth and prompt for authentication.
Complete the OAuth flow to grant access to your Cube deployment.

Available actions

Chat with your Cube AI agent over MCP
Query data and request analysis
Receive responses directly in your MCP client

Example workflows

Ask a data question in natural language
Get SQL generated by the agent
Request summaries, trends, and insights

Troubleshooting

Remote MCP configuration is unavailable: Configure the Remote MCP URL.
Remote MCP OAuth integration is not configured: Enable MCP in Admin → Team & Security → OAuth Integrations.
Remote MCP defaults are not configured: Set defaults in Admin → Remote MCP under Remote MCP Defaults.
redirect_uri is not allowed: For self-hosted or custom clients, update MCP_ALLOWED_REDIRECT_PATTERNS on console-server.