MCP Gateway · Claude
Connect Cube to Claude
Sales, finance and operations staff often wait on the data team for simple numbers. Cube lets them explore analytics data, get SQL written and surface business insights by asking Claude. The gateway URL is a single custom connector, and people only find the servers their role can reach in it.
- Category
- Data & analytics
- Authentication
- None
- Claude
- Web, desktop and mobile
Behind the MCP Gateway
Run Cube MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Cube call inspected and logged.
Set up
Add Cube to Claude in 4 steps
- 01
Add Cube from the catalog
An admin finds Cube in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.
Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.
- 02
Choose who can use Cube
Give teams the
mcp:connectscope on the Cube server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Cube to their gateway on the next call, and removing it takes it away. - 03
Connect Claude
Add the gateway URL as a custom connector, then connect it from Customize > Connectors.
On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.
Each person opens Customize > Connectors and clicks Connect to sign in.
On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.
- 04
Sign in and use Cube from Claude
The first time Claude connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
From then on, Cube's tools appear in Claude, limited to what the person's access allows, and every call lands in the gateway's tool logs.
No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.
Use cases
What Claude users do with Cube
Ask a business question in chat
Ask Claude how a product line or region performed last quarter, and it explores the analytics data in Cube to answer in plain language.
Prepare figures for a review meeting
Before a review, have Claude pull the figures you need from Cube and arrange them into a short summary you can share with the room.
Hand an analyst a starting query
When the data team needs to check or reuse a query, Claude generates the SQL through Cube from your plain-language description.
Control
What Speakeasy can see and stop in Claude
The gateway covers every client the same way. The rest depends on what Claude exposes to Speakeasy.
Tool logs
Gateway
Every Cube call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Cube tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Cube can reject a tool request before it reaches the server, or withhold a result from Claude. MCP-scoped policies are enabled per organization.
Anthropic inference hooks
Claude
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
Conversation import
Claude
Claude conversations can be imported through Anthropic's Compliance API for review after the fact.
- Custom connectors need a Claude plan that supports them.
- Budgets don't cover Claude web and desktop usage.
Questions
Frequently asked questions
Which Claude plans can use Cube through Speakeasy?
Can a prompt about company data be blocked in Claude?
How do Claude users get Cube?
Are Cube calls from Claude logged?
Connect more