Skip to main content
Book a demo

Connect Nimble to Cursor

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

Book a demo Cursor setup guide

Set up

Add Nimble to Cursor in four steps

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

  1. 1

    Approve Nimble in Runlayer

    Add Nimble from the catalog and choose who can use it and which of its tools are allowed.

  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, Nimble’s 27 tools show up in Cursor’s own tool list.

    Cursor setup guide
  3. 3

    Sign in to Nimble

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

  4. 4

    Use Nimble from Cursor

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

Tools

27 Nimble tools in Cursor

Runlayer policy decides which of these Cursor users can call. 16 read data only and 5 can change or delete data.

  • Nimble crawl run

    Nimble Crawl: one-time bulk fetch of a known doc tree or URL list.

  • Nimble crawl status

    Check the status and progress of a running or completed crawl job.

  • Nimble crawl list

    List crawl jobs, optionally filtered by status.

  • Nimble crawl terminate

    Cancel a running or queued crawl job.

  • List extraction templates

    Browse Extraction Templates — reusable, site-specific structured scrapers.

  • Get extraction template

    Get an Extraction Template's input/output schema before running it.

  • Run extraction template

    Run an Extraction Template against 1–few known items (URL or site ID).

  • Generate extraction template

    Generate a new Extraction Template — only when the user explicitly asks to.

See all 27 Nimble 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 Nimble 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