MCP Gateway · Claude Cowork
Connect Cube to Claude Cowork
Cowork can take on analysis that needs several rounds of questions, such as a monthly business review or tracing why a number changed. With Cube behind the Speakeasy MCP Gateway, each step can explore analytics data or generate SQL. Agent hooks send each prompt to Speakeasy before the step runs, and Cowork's OTLP export ties sessions to people.
- Category
- Data & analytics
- Authentication
- None
- Claude Cowork
- Cowork tab in Claude Desktop
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 Cowork 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. Claude Cowork connects to the Cube server's own URL, and the server's authorization decides who can connect and which tools they can call. - 03
Connect Claude Cowork
Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.
New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.
Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.
In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.
Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.
In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.
- 04
Sign in and use Cube from Claude Cowork
The first time Claude Cowork 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 Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.
Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.
Use cases
What Claude Cowork users do with Cube
Draft the monthly business review
Cowork explores analytics data in Cube across several areas of the business, collects the figures, and writes a review draft with the insights it found.
Follow a question through several steps
Give Cowork a question such as why trial conversions changed. It explores the data, generates follow-up queries and reports what it learned at each step.
Document queries for reuse
After answering a question, Cowork writes up the SQL that Cube generated with an explanation, so analysts can rerun or adjust it later.
Control
What Speakeasy can see and stop in Claude Cowork
The gateway covers every client the same way. The rest depends on what Claude Cowork 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 Cowork. MCP-scoped policies are enabled per organization.
Prompt blocking
Claude Cowork
Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.
Session telemetry
Claude Cowork
Cowork's OTLP export ties sessions to people and feeds observability.
Anthropic inference hooks
Claude Cowork
On Claude Enterprise, prompts can be checked before inference (beta).
- Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
- Personal Claude accounts can't be governed in Cowork.
Questions
Frequently asked questions
Does the device agent configure Cube for Cowork?
Can Cube be governed for personal Claude accounts in Cowork?
How do Claude Cowork users get Cube?
Are Cube calls from Claude Cowork logged?
Connect more