Skip to main content
Book a demo

Connect Mintlify to Cursor

Give Cursor governed access to Mintlify’s 35 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Cursor setup guide

Set up

Add Mintlify to Cursor in four steps

Admins approve the server once. Everyone in Cursor then gets it through the same governed connection.

  1. 1

    Add Mintlify to Runlayer

    Mintlify isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 2

    Connect Cursor to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in Cursor, and admins can roll it out org-wide with Auto Sync plus a Cursor team rule. With direct tool listing turned on for your deployment, Mintlify’s 35 tools show up in Cursor’s own tool list.

    Cursor setup guide
  3. 3

    Sign in to Mintlify

    Sign in the way Mintlify requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Mintlify from Cursor

    Mintlify’s approved tools appear in Cursor. Every call is checked against policy and recorded.

Tools

35 Mintlify tools in Cursor

Runlayer policy decides which of these Cursor users can call.

  • Agent review settings

    Change whether agent edits push directly to the deploy branch (push_to_main) or open a pull request (create_pull_request).

  • Checkout

    Select a deployment and open its editor session in one call.

  • Create node

    Insert a node into the navigation tree under parentId (null = root).

  • Delete node

    Remove a node and its subtree from the navigation tree by nodeId.

  • Diff

    Returns the list of changes between current session and main.

  • Discard session

    End the session without creating a PR.

  • Edit page

    String-replace edit on a page Y.

  • Execute code

    Run TypeScript/JavaScript against the Admin MCP dashboard SDK inside a sandboxed Cloudflare isolate.

See all 35 Mintlify tools

Control

What Runlayer can see and stop in Cursor

Some controls apply to every client at the gateway. Others depend on what Cursor exposes to Runlayer.

  • Gateway policy (available)

    Every Mintlify call from Cursor passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Cursor as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Cursor runs it, including calls to MCP servers.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Cursor’s model sees it.

  • Redact output in place (not available)

    Cursor cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

In Cursor

  • Runlayer cannot tell Agents Window sessions apart from regular IDE sessions.
  • The Cursor CLI sends fewer session events than the IDE, but Runlayer’s allow and deny decisions still apply.

Frequently asked questions

Connect more

Find another combination