Skip to main content
Back to the DeepWiki MCP server

MCP Gateway · Cursor

DeepWiki icon

Connect DeepWiki to Cursor

When code you depend on behaves in a way you didn't expect, the answer is usually in someone else's repository. With DeepWiki behind the Speakeasy MCP Gateway, Cursor can read wiki docs for public GitHub repositories and ask questions about them next to your own code. Speakeasy's Cursor hooks fail closed, and each hook event carries the developer's email.

Category
Developer tools
Tools
3
Authentication
None
Cursor
Editor and terminal

Behind the MCP Gateway

Run DeepWiki MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every DeepWiki call inspected and logged.

Deploy on MCP Gateway

Set up

Add DeepWiki to Cursor in 4 steps

  1. 01

    Add DeepWiki from the catalog

    An admin finds DeepWiki 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.

  2. 02

    Choose who can use DeepWiki

    Give teams the mcp:connect scope on the DeepWiki server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds DeepWiki 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 DeepWiki from Cursor

    The first time Cursor connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    From then on, DeepWiki'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 DeepWiki

Follow a dependency's internals while debugging

When behavior inside a public dependency surprises you, Cursor asks DeepWiki how that code path works and explains it beside the file you're debugging.

ask_question

Map a repository before forking it

Cursor lists the documentation topics for a public GitHub repository, giving you an outline of its parts before you fork or vendor it.

read_wiki_structure

Borrow a well-known project's pattern

Cursor reads how an established open source project organizes its configuration or tests, then applies the same approach to the file you're editing.

read_wiki_contents

Tools

3 tools

Each DeepWiki tool can be allowed or denied per team and role at the MCP Gateway before Cursor sees it.

read_wiki_structure

Get a list of documentation topics for a GitHub repository.

read_wiki_contents

View documentation about a GitHub repository.

ask_question

Ask any question about a GitHub repository and get an AI-powered, context-grounded response.

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 DeepWiki call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the DeepWiki tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to DeepWiki 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

Do developers need a DeepWiki credential in Cursor?
No. Agents never hold a DeepWiki credential. Sessions sign in to the gateway through your identity provider, and access ends when someone leaves the directory.
What do Cursor users do after the DeepWiki plugin changes?
After a plugin update, members run Developer: Reload Window to load it.
How do Cursor users get DeepWiki?
An admin adds DeepWiki 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 DeepWiki tools their access allows.
Are DeepWiki calls from Cursor logged?
Yes. DeepWiki 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

DeepWiki in other clients

AI everywhere.

Control here.