Skip to main content
Book a demo

Connect Gumloop to Cursor

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

Book a demo Cursor setup guide

Set up

Add Gumloop to Cursor in four steps

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

  1. 1

    Approve Gumloop in Runlayer

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

    Cursor setup guide
  3. 3

    Sign in to Gumloop

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

  4. 4

    Use Gumloop from Cursor

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

Tools

45 Gumloop tools in Cursor

Runlayer policy decides which of these Cursor users can call.

  • List agents

    List agents in your Gumloop account, with optional search and workspace filtering.

  • Get agent

    Fetch a single Gumloop agent's configuration by its ID.

  • Ask gummie

    Ask questions and get AI-powered answers from Gumloop documentation.

  • Attach agent MCP server

    Attach an MCP server (connector) to a Gumloop agent, or update its configuration if already attached.

  • Attach agent skills

    Attach one or more existing skills to a Gumloop agent.

  • Call MCP tool

    Execute a single tool on a connected MCP server.

  • Cancel session

    Cancel an in-progress Gumloop agent session.

  • Create agent

    Create a new Gumloop agent with a name, model, and optional configuration.

See all 45 Gumloop 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 Gumloop 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