Skip to main content
Book a demo

Connect Ordinal to VS Code

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

Book a demo VS Code setup guide

Set up

Add Ordinal to VS Code in four steps

Admins approve the server once. Everyone in VS Code 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 VS Code to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, Ordinal’s 50 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).

    VS Code 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 VS Code

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

Tools

50 Ordinal tools in VS Code

Runlayer policy decides which of these VS Code 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 VS Code

Some controls apply to every client at the gateway. Others depend on what VS Code exposes to Runlayer.

  • Gateway policy (available)

    Every Ordinal call from VS Code passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, VS Code 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 VS Code runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before VS Code’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a tool’s output in VS Code and pass the rest through.

Frequently asked questions

Connect more

Find another combination