Connect Monday to GitHub Copilot CLI
Give GitHub Copilot CLI governed access to Monday’s 101 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Monday 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 Monday in Runlayer
Add Monday 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 Monday’s 101 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
GitHub Copilot CLI setup guide - 3
Sign in to Monday
Sign in the way Monday requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Monday from GitHub Copilot CLI
Monday’s approved tools appear in GitHub Copilot CLI. Every call is checked against policy and recorded.
Tools
101 Monday tools in GitHub Copilot CLI
Runlayer policy decides which of these GitHub Copilot CLI users can call.
Agent catalog
Browse the account-wide catalog of available trigger types and skills for monday platform agents.
Read all API
Execute read-only GraphQL queries against the monday.com API.
Write all API
Execute GraphQL mutations against the monday.com API to create, update, or delete data.
All Monday API
Execute any monday.com API operation by generating GraphQL queries and mutations dynamically.
All widgets schema
Fetch complete JSON Schema 7 definitions for all available widget types in monday.com.
Board insights
Allows you to calculate insights about board's data by filtering, grouping and aggregating columns.
Change item column values
Change the column values of a single item on a monday.com board.
Connect external agent
Connect a custom external agent (an agent running on your own server/infra) to monday.com.
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 Monday 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