Skip to main content
Book a demo

Connect NetSuite to Cursor

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

Book a demo Cursor setup guide

Set up

Add NetSuite to Cursor in four steps

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

  1. 1

    Approve NetSuite in Runlayer

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

    Cursor setup guide
  3. 3

    Sign in to NetSuite

    Each user signs in to NetSuite with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use NetSuite from Cursor

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

Tools

17 NetSuite tools in Cursor

Runlayer policy decides which of these Cursor users can call.

  • Ns create record

    Create a new record in NetSuite.

  • Ns get accounting books

    Returns all accounting books available to the user for report execution.

  • Ns get accounting contexts

    Returns all accounting contexts available to the user for report execution.

  • Ns get nexus IDS

    Returns all nexus IDs available to the user for report execution.

  • Ns get record

    Retrieve a record from NetSuite.

  • Ns get record type metadata

    Get metadata information about all record types or from a specific record type including available fields and their types

  • Ns get subsidiaries

    Returns all the subsidiaries available to the user for the report tool.

  • Ns get suite ql metadata

    Retrieves SuiteQL metadata for either all record types list or a specific record type and should be called before runCustomSuiteQL to discover which fields you can safely select, filter, and sort on.

See all 17 NetSuite 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 NetSuite 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