Skip to main content
Back to the Guru MCP server

MCP Gateway · Cursor

Guru icon

Connect Guru to Cursor

Style guides and review checklists are easier to follow when they appear next to the file you are changing. With Guru connected through the Speakeasy MCP Gateway, Cursor's agent can pull those cards into the editor. Cursor hooks send each prompt and tool call to Speakeasy for an allow or deny and fail closed.

Category
Communication
Tools
6
Authentication
OAuth
Cursor
Editor and terminal

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

    Add the gateway to Cursor in one click from the Organization Gateway page.

    On the Organization Gateway page in Speakeasy, choose Cursor under Install.

    Click Add to Cursor to add the gateway to Cursor's MCP settings, then sign in when Cursor prompts you.

  4. 04

    Sign in and use Guru from Cursor

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

For a whole team, a Cursor team admin imports the plugin marketplace under Settings > Plugins > Import and turns on Serve Marketplace From Cursor, so members install without GitHub access.

Use cases

What Cursor users do with Guru

Apply the review checklist

Before you open a pull request, ask Cursor to find the team's code review checklist in Guru and walk through the current diff against each item.

guru_search_documentsguru_get_card_by_id

Answer a setup question in the editor

Stuck on a local environment variable or a test fixture? Ask Cursor, and it generates an answer from the knowledge base rather than a list of links.

guru_answer_generation

Correct an outdated card

If a Guru card describes an API the code no longer matches, Cursor rewrites the affected section and saves the card with the current behavior.

guru_update_card

Tools

6 tools

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

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

Prompt and tool-call blocking

Cursor

Cursor hooks send each prompt and tool call to Speakeasy, which allows or denies it before Cursor runs it, and fail closed.

User attribution

Cursor

Every Cursor hook event carries the user's email.

Budgets

Cursor

Spend limits can block Cursor traffic once a budget is reached. Connect the Cursor Admin API for dollar spend.

Device agent and MDM

Cursor

The device agent installs the marketplace and plugins and reapplies them every minute.

  • Cursor Cloud agents need a checked-in .cursor/hooks.json. Session and MCP-specific hooks don't run there.
  • After a plugin update, members run Developer: Reload Window.

Questions

Frequently asked questions

How do Guru plugin updates reach Cursor?
The device agent installs the marketplace and plugins and reapplies them every minute. After a plugin update, members run Developer: Reload Window.
Can Cursor spend be capped while using Guru?
Spend limits can block Cursor traffic once a budget is reached. Connect the Cursor Admin API for dollar spend.
How do Cursor users get Guru?
An admin adds Guru from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway to Cursor in one click from the Organization Gateway page. Each person then sees only the Guru tools their access allows.
Are Guru calls from Cursor 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.