Connect Ordinal to GitHub Copilot CLI
Give GitHub Copilot CLI governed access to Ordinal’s 50 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Ordinal to GitHub Copilot CLI in four steps
Admins approve the server once. Everyone in GitHub Copilot CLI then gets it through the same governed connection.
- 1
Approve Ordinal in Runlayer
Add Ordinal from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect GitHub Copilot CLI to Runlayer
Users add the Runlayer Plugin to GitHub Copilot CLI by following Runlayer’s setup guide. GitHub Copilot CLI reaches Ordinal’s 50 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
GitHub Copilot CLI setup guide - 3
Sign in to Ordinal
An admin adds Ordinal credentials to Runlayer once. They never sit in the client’s configuration.
- 4
Use Ordinal from GitHub Copilot CLI
Ordinal’s approved tools appear in GitHub Copilot CLI. Every call is checked against policy and recorded.
Tools
50 Ordinal tools in GitHub Copilot CLI
Runlayer policy decides which of these GitHub Copilot CLI 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.
Control
What Runlayer can see and stop in GitHub Copilot CLI
Some controls apply to every client at the gateway. Others depend on what GitHub Copilot CLI exposes to Runlayer.
Gateway policy (available)
Every Ordinal call from GitHub Copilot CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, GitHub Copilot CLI 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 or permission request before GitHub Copilot CLI runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before GitHub Copilot CLI’s model sees it.
Redact output in place (available)
Runlayer can mask sensitive parts of a successful tool’s output in GitHub Copilot CLI and pass the rest through.
In GitHub Copilot CLI
- When a tool fails, Runlayer records the error but cannot replace it.
Frequently asked questions
Connect more