Aleph
Query live FP&A data, build reports and update dashboards from your AI assistant.
Query Cube semantic models, build dashboards and edit data models from an AI agent.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Cube MCP server connects a Cube semantic layer to Claude and any MCP-compatible agent. Its 23 tools run queries against governed data models, author dashboards and reports, edit the data model itself, and manage pre-aggregations. Model edits are confined to a personal dev branch by design.
Connection verified
Connection checked by Agentman on .
Listed in Anthropic’s Connectors Directory at community tier — a listing, not a partner-level review.
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
valid: true is a compile check, not a correctness check. Verify on the dev branch with runQuery.deleteReport acts directly.Premium or Enterprise. Cube states the MCP server is available on those plans only, and that users need the Viewer role or higher to interact with it. Which tools a user actually sees depends on their role, so two people on the same deployment can be offered different capabilities from the same endpoint.
No, by construction. Cube documents that every model write goes to a personal dev branch named dev-user-hash, and that the write tools reject any branch that is not a dev branch, so the deploy branch is never writable over MCP. Promotion to production requires a person committing the branch in the Cube UI.
It exposes no commit tool at all. Cube states this is deliberate: an AI client can prepare changes on a dev branch, but only a person can ship them, by committing from the Cube UI. Combined with dev-branch-only writes, that keeps the promotion step human without relying on a client approval prompt.
No. Cube documents cubecloud.dev/mcp as the same URL for every account, deployment and region, identifying your account from the OAuth token and routing each request to whichever deployment serves it. Region-specific endpoints also exist under Admin then MCP Server, but the single URL is the documented default.
Only that the model compiles. Cube is explicit that it does not mean the edit is correct, and recommends passing the dev branchName to runQuery to check the edit returns the right data. Verification happens on the branch before a merge rather than after, which is the point of the dev-branch workflow.
No. Cube documents that tool registration is permission-gated: the six model-editing tools, getBranchDiff, getDeploymentEnv and both pre-aggregation tools are offered only to users whose role allows editing the semantic model. A Viewer never sees them at all, so the restriction is on tool visibility rather than on call failure.
.md variant; retrieved 2026-09-13). docs.cube.dev/robots.txt carries Content-Signal: ai-train=yes, search=yes, ai-input=yes — an explicit publisher opt-in to AI synthesis, recorded here because we rely on it. · retrieved 2026-09-13https://cubecloud.dev/mcp — HTTP 401 with a www-authenticate Bearer challenge, and RFC 9728 metadata at https://cubecloud.dev/.well-known/oauth-protected-resource/mcp returning the single scope mcp-agent-access (2026-09-13) · retrieved 2026-09-13Connect Cube once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.