Skip to main content
Book a demo

Connect Carta to Cursor

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

Book a demo Cursor setup guide

Set up

Add Carta to Cursor in four steps

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

  1. 1

    Approve Carta in Runlayer

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

    Cursor setup guide
  3. 3

    Sign in to Carta

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

  4. 4

    Use Carta from Cursor

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

Tools

18 Carta tools in Cursor

Runlayer policy decides which of these Cursor users can call.

  • Call tool

    Run a Carta tool that search_tools found.

  • Cap table chart

    Show a visual cap table summary with ownership breakdown by share class.

  • Discover

    List available Carta commands or views across all domains.

  • Fetch

    Execute a named Carta read command.

  • Get current user

    Get the currently authenticated Carta user's profile.

  • List accounts

    List all companies and organizations the current user has access to.

  • List contexts

    Show which firms you have access to in Carta Fund Admin and which one is currently active.

  • List resources

    List all available resources and resource templates.

See all 18 Carta 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 Carta 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