MCP Gateway · Claude
Connect Glean to Claude
People across the company use Claude to answer questions that depend on internal knowledge: policies, product details, past projects. With Glean connected through the Speakeasy gateway, Claude can search that knowledge and write the answer. An Owner adds the gateway once as a custom connector, and each person connects it from Customize > Connectors with no client ID or secret.
- Category
- Productivity
- Authentication
- None
- Claude
- Web, desktop and mobile
Behind the MCP Gateway
Run Glean MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Glean call inspected and logged.
Set up
Add Glean to Claude in 4 steps
- 01
Add Glean from the catalog
An admin finds Glean 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 Glean
Give teams the
mcp:connectscope on the Glean server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Glean 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 Glean 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, Glean'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 Glean
Answer a policy question
Ask Claude what the travel, expense or leave policy says about your situation, and it searches Glean for the current policy and answers from it.
Build a customer briefing
Before a meeting, account managers ask Claude to search Glean for past proposals, notes and documents about the customer and turn them into a one-page brief.
Find who worked on a project
Ask Claude who led a past project or launch, and it searches Glean for the documents and people connected to it.
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 Glean call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Glean tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Glean 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
Can Claude Enterprise check prompts before searching Glean?
Can Claude conversations that used Glean be reviewed later?
How do Claude users get Glean?
Are Glean calls from Claude logged?
Connect more