Monday MCP

Live

OAUTH 2.0

PROJECT MANAGEMENT

Project Management

Connect to the monday.com MCP server to manage boards, items, columns, docs, and workflows directly from your AI agents.

  • Acts as the user: Every tool call runs as the authorizing user. Access and audit trail stay intact.
  • Credentials stay vaulted: AES-256 encrypted, resolved at request time, never stored in LLM context.
  • Scoped before every call: Per-user permissions enforced automatically. 90-day audit trail included.
Monday MCP
agent · Acme Q3
Run
Agentcatalog in Monday MCP
S
mondaymcp_agentcatalog
85ms
Monday MCP agent
Browse the account-wide catalog of available trigger types and skills for monday platform agents. read-only — no agent.
Sources: Monday MCP
mondaymcpmcp
1 tool call
18:29
Message Claude...

Monday MCP tools for AI agents

CALL ANY TOOL
12 tools covering allwidgetsschema, agentcatalog, allmondayapi.
mondaymcp_agentcatalog
Agentcatalog
Browse the account-wide catalog of available trigger types and skills for monday platform agents. READ-ONLY — no agent_id required. Use this tool to discover what's available BEFORE wiring anything to a specific agent. ACTIONS: - list_triggers: { block_reference_ids? } — returns available trigger types. Each entry has block_reference_id (required for manage_agent_triggers action:"add"), name, description, field_schemas (describes field_values shape), and required_fields (fields to collect from the user). Note: only triggers that can be added programmatically appear here. OAuth/3rd-party triggers (Slack, Gmail, Salesforce, etc.) require user setup in the monday.com UI and will not appear here. - list_skills: {} — returns available skills with id, name, description. Never guess or invent a skill id — always look it up here before calling manage_agent_skills action:"add". USAGE EXAMPLES: - List all trigger types: { "action": "list_triggers" } - Fetch specific trigger: { "action": "list_triggers", "block_reference_ids": ["some-block-ref-id"] } - List all skills: { "action": "list_skills" } RELATED TOOLS: - manage_agent_triggers — use block_reference_id from list_triggers to attach a trigger to a specific agent - manage_agent_skills — use skill id from list_skills, or action:"create" to author a new skill, then attach to an agent - manage_agent — manage the agent entity itself (create, update, delete, activate, etc.)
Parameters
Name
Type
Required
Description
action
string
Required
"list_triggers" — fetch available trigger types with block_reference_id, field_schemas, and required_fields. Call before using manage_agent_triggers action:"add". "list_skills" — fetch available skills with id, name, description. Call before using manage_agent_skills action:"add".
block_reference_ids
array
Optional
Used with action:"list_triggers". Fetch specific trigger types by block_reference_id. Omit to return all trigger types.
mondaymcp_allwidgetsschema
Allwidgetsschema
mondaymcp_changeitemcolumnvalues
Changeitemcolumnvalues
mondaymcp_createboard
Createboard
mondaymcp_createdashboard
Createdashboard
mondaymcp_createfolder
Createfolder
mondaymcp_createformsubmission
Createformsubmission
mondaymcp_createitem
Createitem
mondaymcp_createview
Createview
mondaymcp_createwidget
Createwidget
mondaymcp_createworkspace
Createworkspace
mondaymcp_formquestionseditor
Formquestionseditor
mondaymcp_getassetuploadurl
Getassetuploadurl
mondaymcp_getautomationstatistics
Getautomationstatistics
mondaymcp_getboardinfo
Getboardinfo
mondaymcp_getform
Getform
mondaymcp_getgraphqlschema
Getgraphqlschema
mondaymcp_getnotetakermeetings
Getnotetakermeetings
mondaymcp_getsprintsummary
Getsprintsummary
mondaymcp_getupdates
Getupdates
mondaymcp_listautomations
Listautomations
mondaymcp_listworkspaces
Listworkspaces
mondaymcp_manageagentskills
Manageagentskills
mondaymcp_manageautomations
Manageautomations
mondaymcp_planworkflow
Planworkflow
mondaymcp_readdocs
Readdocs
mondaymcp_search
Search
mondaymcp_updatefolder
Updatefolder
mondaymcp_updateview
Updateview
mondaymcp_updateworkflow
Updateworkflow

For more tools, view docs.

Build your Agent
Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.
Python · LlamaIndex
from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="mondaymcp")

mcp = MultiServerMCPClient({
"mondaymcp": {
"url": "https://mcp.scalekit.com/mondaymcp",
"headers": {"Authorization": "Bearer " + token}
}
})
tools = await mcp.get_tools()
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "mondaymcp" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/mondaymcp
// Pass: Authorization: Bearer + token
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "mondaymcp" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/mondaymcp
// Pass: Authorization: Bearer + token
from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="mondaymcp")
# Connect to MCP at https://mcp.scalekit.com/mondaymcp
# Pass: Authorization: Bearer + token
Try these prompts
Copy any prompt into your agent. Each maps directly to a Monday tool. Click to copy, paste into your agent, done.
Get started
Copy the prompt
Copied
This tool returns the boards, docs and folders in a workspace and which folder they are in?
Copy the prompt
Copied
Update an existing workspace in monday.com?
Advanced
Copy the prompt
Copied
Updates an existing workflow draft using an AI agent?
Copy the prompt
Copied
Update an existing table-type board view — change its name, filters, sort, tags, or table-specific settings (column vi?
SEE HOW AUTH WORKS
Your users connect once. Their Monday credentials stay vaulted, every call is scope-checked, and every action is logged.
1
Authorize
Your user connects
Monday MCP
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Monday MCP
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Monday MCP
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Monday MCP
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other connectors.
Engineering Teams
Engineering standup agent
Pulls commits from GitHub and GitLab, tracks issue movement in Jira, and posts a per-engineer standup brief to Slack. Each engineer's activity is read on their own delegated OAuth.
Engineering Teams
DevOps assistant agent
Polls GitHub for failing checks and stale PRs, opens Linear issues for the ones that need work, and posts a daily digest to Slack. It acts as the engineer, not a shared service account.
Engineering Teams
Slack triage
Polls Slack for new messages, classifies bugs and support requests with a LangGraph router, files GitHub issues or Zendesk tickets, and confirms in the thread.
People Ops and HR teams
Performance review collector
Collects review feedback from Airtable and Google Forms scoped to each manager's direct reports, writes per-employee summaries to Notion, and DMs the manager a Slack digest.
Test other agents
See the same per-user auth pattern across other connectors.
ENGINEERING
Engineering standup agent
Pull commits from GitHub and GitLab, track Jira issue movement, and post a per-engineer standup brief to Slack.
ENGINEERING
DevOps assistant agent
Poll GitHub for failing checks and stale pull requests, open Linear issues for the ones that need work, and digest to Slack.
ENGINEERING
Slack triage agent
Classify new Slack messages as bugs or support requests, file the GitHub issue or Zendesk ticket, and reply in the thread.
PEOPLE OPS
Performance review collector agent
Collect review feedback from Airtable and Google Forms per manager, summarise each report in Notion, and DM the digest in Slack.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.
// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
One connector today. Ten tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions

Does the agent access Monday as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Monday OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Monday?
Yes. Pass a tool name filter to listScopedTools so the project management agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Monday.

What happens when a user revokes Monday access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Does the agent respect monday.com board permissions?
Yes. Board reads, column updates, and automations run as the authorizing user. Private boards, guest scopes, and workspace roles hold on every call.

Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""mondaymcp"": {
""url"": ""https://mcp.scalekit.com/mondaymcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.mondaymcp]
url = ""https://mcp.scalekit.com/mondaymcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""mondaymcp"": {
""url"": ""https://mcp.scalekit.com/mondaymcp"",
""type"": ""http""
}
}
}