Skip to main content
Book a demo

Connect Ordinal to Cursor

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

Book a demo Cursor setup guide

Set up

Add Ordinal to Cursor in four steps

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

  1. 1

    Approve Ordinal in Runlayer

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

    Cursor setup guide
  3. 3

    Sign in to Ordinal

    An admin adds Ordinal credentials to Runlayer once. They never sit in the client’s configuration.

  4. 4

    Use Ordinal from Cursor

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

Tools

50 Ordinal tools in Cursor

Runlayer policy decides which of these Cursor users can call.

  • Get analytics cpm

    Get CPM Values - Retrieve the current CPM (Cost Per Mille) values used for EMV calculations across all platforms.

  • Update analytics cpm

    Update CPM Values - Update the CPM values used for EMV calculations.

  • Analytics linkedin followers

    Retrieve follower count history for a LinkedIn profile.

  • Analytics linkedin posts

    Retrieve post analytics for a LinkedIn profile within a date range.

  • Analytics x followers

    Retrieve follower count history for an X profile.

  • Analytics x posts

    Retrieve post analytics for an X profile within a date range.

  • Create approvals

    Create one or more approval requests for a post.

  • Delete approvals

    Delete an approval request.

See all 50 Ordinal 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 Ordinal 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