Skip to main content
Back to the Guru MCP server

MCP Gateway · Claude Cowork

Guru icon

Connect Guru to Claude Cowork

Keeping a knowledge base current is slow work that fits a long Cowork session. With Guru delivered through a plugin from Speakeasy's synced marketplace, Cowork can go through a set of cards, check them against newer material and draft the fixes. Agent hooks send each prompt to Speakeasy before the step runs.

Category
Communication
Tools
6
Authentication
OAuth
Claude Cowork
Cowork tab in Claude Desktop

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 Cowork 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. Claude Cowork connects to the Guru server's own URL, and the server's authorization decides who can connect and which tools they can call.

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

  4. 04

    Sign in and use Guru 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.

    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 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 Guru

Review a collection of stale cards

Give Cowork a topic like pricing. It finds every related card, reads each one in full, and lists the statements that conflict with the current price sheet.

guru_search_documentsguru_get_card_by_id

Turn a handbook into draft cards

Hand Cowork a long internal handbook and have it split the content into focused draft cards in Guru, one per question people actually ask.

guru_create_draft

Compare answers across knowledge agents

Cowork asks the same question of the sales and support knowledge agents and reports where their answers differ, so owners can settle on one.

guru_list_knowledge_agentsguru_answer_generation

Tools

6 tools

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

The gateway covers every client the same way. The rest depends on what Claude Cowork 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 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

What does an admin set up before Cowork can use Guru?
In Claude's Organization settings > Plugins & skills, the admin syncs the plugin repository from GitHub, marks the observability plugin Required and makes the plugin that carries Guru available. The OTLP endpoint is set in Cowork's Monitoring settings.
Does the device agent manage Guru in Cowork?
No. Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
How do Claude Cowork users get Guru?
An admin adds Guru from the Speakeasy MCP Catalog and grants access by team or role. Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork. Each person then sees only the Guru tools their access allows.
Are Guru calls from Claude Cowork 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.