MCP Gateway · Claude
Connect Guru to Claude
Support and sales teams keep their answers in Guru so everyone tells customers the same thing. Added to Claude as a custom connector through the Speakeasy MCP Gateway, Guru lets people ask Claude a question and get an answer built from those cards. Each person only sees the servers their role can reach.
- Category
- Communication
- Tools
- 6
- Authentication
- OAuth
- Claude
- Web, desktop and mobile
Behind the MCP Gateway
Run Guru MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Guru call inspected and logged.
Set up
Add Guru to Claude in 4 steps
- 01
Add Guru from the catalog
An admin finds Guru 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.
Guru uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.
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 Guru
Give teams the
mcp:connectscope on the Guru server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Guru 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 Guru from Claude
The first time Claude connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Guru needs its own OAuth grant, so each person connects it once. Until they do, Guru calls fail while the rest of the gateway keeps working.
From then on, Guru'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 Guru
Answer a customer question accurately
Paste a customer's question into Claude. It asks Guru's support knowledge agent and returns an answer from the knowledge base that you can adapt into a reply.
Capture a new answer as a card
When a question has no good answer yet, write one with Claude and save it to Guru as a draft card for the knowledge owner to review.
Find the right policy document
Ask Claude whether there are cards on refunds or data retention, and get the matching documents to open rather than a summary.
Tools
6 tools
Each Guru tool can be allowed or denied per team and role at the MCP Gateway before Claude sees it.
guru_answer_generation
Generate direct answers to questions using the knowledge base. Use when users ask specific questions ('What is X?', 'How do I Y?'). Provides comprehensive answers, not just documents.
guru_create_draft
Create a Draft of a Card in Guru. Use when the users ask to save the content to Guru using a Draft
guru_search_documents
Find and retrieve specific documents, sources or cards. Use when users want to discover existing content ('find me docs on X', 'do we have cards about Y'). Returns documents for browsing, not answers.
guru_update_card
Update the content of an existing card. Use when users want to modify existing card content.
guru_list_knowledge_agents
Get available knowledge agents and their IDs. Always call this first before using guru_search_documents or guru_answer_generation tools, as both require an agentId parameter. Each agent has different expertise areas and data sources configured.
guru_get_card_by_id
Get full card content in original HTML format by card ID
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 Guru call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Guru tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Guru 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 Guru through Speakeasy?
Do Speakeasy budgets apply to Guru use in Claude?
How do Claude users get Guru?
Are Guru calls from Claude logged?
Connect more