Skip to main content
Back to the Guru MCP server

MCP Gateway · Claude Code

Guru icon

Connect Guru to Claude Code

Engineering conventions, on-call runbooks and architecture notes often sit in Guru cards rather than the repo. With Guru behind the Speakeasy MCP Gateway, Claude Code can ask the knowledge base a question mid-task and get an answer drawn from those cards. Agent hooks check each prompt and tool call before Claude Code runs it.

Category
Communication
Tools
6
Authentication
OAuth
Claude Code
CLI

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.

Deploy on MCP Gateway

Set up

Add Guru to Claude Code in 4 steps

  1. 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.

  2. 02

    Choose who can use Guru

    Give teams the mcp:connect scope 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.

  3. 03

    Connect Claude Code

    Add the organization gateway as an HTTP MCP server, then authenticate from /mcp.

    Run the command below with your organization gateway URL.

    Open /mcp in Claude Code and choose Authenticate to sign in.

    claude mcp add --transport http --scope user \
      'speakeasy' \
      'https://<organization host>/mcp/gateway/<organization slug>'
  4. 04

    Sign in and use Guru from Claude Code

    The first time Claude Code 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 Code, limited to what the person's access allows, and every call lands in the gateway's tool logs.

To roll it out to a whole team, publish the server in a plugin and register the plugin marketplace in Claude Code's managed settings, so every member gets it without running the command. The device agent can also write and reapply these settings on each laptop.

Use cases

What Claude Code users do with Guru

Ask how the team does it

Before adding a new endpoint, have Claude Code ask Guru's engineering knowledge agent how the team versions APIs, then follow the answer instead of guessing from old code.

guru_list_knowledge_agentsguru_answer_generation

Fix the runbook with the code

When a change alters how a service restarts or scales, Claude Code opens the matching runbook card and updates its content in the same session as the commit.

guru_get_card_by_idguru_update_card

Check for existing documentation

Ask Claude Code whether Guru already has cards on the library you are about to adopt, so you reuse the team's notes rather than starting a new page.

guru_search_documents

Tools

6 tools

Each Guru tool can be allowed or denied per team and role at the MCP Gateway before Claude Code 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 Code

The gateway covers every client the same way. The rest depends on what Claude Code 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 Code. MCP-scoped policies are enabled per organization.

Prompt and tool-call blocking

Claude Code

Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Claude Code runs it.

User attribution

Claude Code

Claude Code's OpenTelemetry exporter ties each session to a named person. Without it, activity can't be attributed.

Budgets

Claude Code

Spend limits can block Claude Code traffic once a budget is reached.

Device agent and MDM

Claude Code

The device agent installs the marketplace, plugin and telemetry settings and reapplies them every minute. It deploys through MDM.

Anthropic inference hooks

Claude Code

On Claude Enterprise, prompts can be checked before inference with nothing installed on the device (beta).

  • Claude Code on the web doesn't use the laptop setup. It needs the device agent in a shared Anthropic-hosted environment.
  • Plugin marketplace URLs for Claude Code carry an access token, so share install snippets only through a private channel.

Questions

Frequently asked questions

Can Claude Code edit Guru cards, or only read them?
That depends on the role. Each of the six Guru tools can be allowed or denied per team at the MCP Gateway, so a team can use search and answers without guru_update_card or guru_create_draft.
Is Guru usage in Claude Code tied to a named developer?
With Claude Code's OpenTelemetry exporter configured, each session is tied to a named person. Without it, activity can't be attributed.
How do Claude Code users get Guru?
An admin adds Guru from the Speakeasy MCP Catalog and grants access by team or role. Add the organization gateway as an HTTP MCP server, then authenticate from /mcp. Each person then sees only the Guru tools their access allows.
Are Guru calls from Claude Code logged?
Yes. Guru calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Guru in other clients

AI everywhere.

Control here.