Connect Monday to Claude Code
Give Claude Code governed access to Monday’s 101 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Monday to Claude Code in four steps
Admins approve the server once. Everyone in Claude Code 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 Claude Code to Runlayer
Runlayer’s CLI installs the Runlayer Plugin natively in Claude Code, and an Anthropic org install also reaches Claude Code. With direct tool listing turned on for your deployment, Monday’s 101 tools show up in Claude Code’s own tool list (supported Claude Code versions).
Claude Code 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 Claude Code
Monday’s approved tools appear in Claude Code. Every call is checked against policy and recorded.
Tools
101 Monday tools in Claude Code
Runlayer policy decides which of these Claude Code 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 Claude Code
Some controls apply to every client at the gateway. Others depend on what Claude Code exposes to Runlayer.
Gateway policy (available)
Every Monday call from Claude Code passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Claude 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.
Anthropic inference hooks (available)
With Claude Enterprise, Anthropic sends each governed Claude Code prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).
OTLP telemetry (available)
Claude Code can export OpenTelemetry logs to Runlayer for observe-only session reconstruction.
Stop a call before it runs (available)
Runlayer can deny a tool call before Claude Code runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Claude Code’s model sees it.
Redact output in place (available)
Runlayer can mask sensitive parts of a tool’s output in Claude Code and pass the rest through.
In Claude Code
- When a tool fails, Runlayer records the error but cannot hide it.
Frequently asked questions
Connect more