Skip to main content
Book a demo

Connect Devin to Cursor

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

Book a demo Cursor setup guide

Set up

Add Devin to Cursor in four steps

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

  1. 1

    Add Devin to Runlayer

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

    Cursor setup guide
  3. 3

    Sign in to Devin

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

  4. 4

    Use Devin from Cursor

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

Tools

24 Devin tools in Cursor

Runlayer policy decides which of these Cursor users can call.

  • Ask wiki question

    Ask any question about a GitHub repository's codebase and get an AI-powered answer grounded in its DeepWiki.

  • Automation manage

    Manage Devin automations.

  • Billing tag manage

    Manage Devin billing tags (groupings of Devin sessions for usage tracking) with a single action-based tool: list/get/create tags, assign sessions one at a time or in bulk (up to 500 per call, sent in…

  • Blueprint test

    Test a candidate blueprint YAML in an authoring VM: start → run initialize → fix → run initialize again (clean VM) → run maintenance → then persist with update_environment_config.

  • Campaign manage

    Read and publish a bot's campaign: its plan, its append-only readings and its status.

  • Code scan manage

    Manage Devin code scans (sometimes referred to as "security scans" or "Devin Security Swarm").

  • Find setting

    Find a Devin webapp setting and get a deep-link URL to it.

  • Knowledge manage

    Manage Devin knowledge notes and suggestions via a single action-based tool.

See all 24 Devin 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 Devin 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