Claude monday.com connectorWhat Claude can do in your monday.com account.
The Claude monday.com connector exposes 33 tools. 6 read boards, docs and updates, 5 can post, file or move things, and 22 carry names no official text describes. Here: what is documented, what you approve, and who can switch it off.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can reach your monday.com
Status meetings stop being a tour of boards. You ask Claude what is going on, it searches your workspaces, reads item updates and docs, and answers in the chat. When a note or a doc should land in monday.com, it can put it there, inside what your own account can see. monday.com states it never reaches past your existing permissions.
Catch up on a project without opening ten boards. search finds the board, doc, form or folder you mean, get_updates pulls the comments on an item with their authors and dates, and read_docs returns a monday doc as text Claude can summarise.
Leave the trace where the team works. create_update posts a comment on an item, create_doc writes a spec or a retro as a monday doc, and create_folder or create_workspace give a new initiative its own place. move_object tidies folders and boards once the dust settles.
Know who is who. list_users_and_teams and get_user_context tell Claude which people, teams and boards matter to you, so it does not guess an owner.
Now the part the directory sheet does not say. Twenty-two of its tool names, including create_items_and_tasks and all_api_write, do not appear in monday.com's own tool article, last updated in May 2026. We describe none of them. An admin switch on the monday.com side can also block the whole thing. And nothing runs by itself: no tool starts when an item changes status. For that kind of background job, an automation tool is the right trade, and the Integrations hub gathers that side.
The vocabulary in one minute
Five words you will run into while plugging monday.com into Claude.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work in that account while it answers you.
- Tool
- One named action a connector opens to Claude. It picks the ones it needs by itself, and the directory sheet lists them by name.
- Authorization
- The sign-in screen of the service itself, where you hand Claude the access it will use. Granted once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it goes through with something that changes your account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on. It is what lets an assistant like Claude talk to an outside service such as monday.com.
Connect monday.com to Claude in three steps
- 01
Find monday.com in Claude
In Claude, open Customize, then Connectors, and look for monday.com in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on first, before each member can sign in.
- 02
Start the connection
Click Connect on the monday.com row, then sign in to monday.com in the window it opens itself. If the link ever breaks, use Disconnect and connect again from the same place.
- 03
Read the authorization screen
Read monday.com's authorization screen before you accept. It belongs to monday.com, not to Claude, and it sets what the access covers. You can take that access back later from your monday.com account.
The 33 Claude monday.com connector tools, by what they do
monday.com gives Claude 33 tools: 6 that read your account, 5 that change something in it, and 22 no official source describes.
Three groups: what Claude reads, what it can change, and what no official source describes. Tool names stay exactly as Claude shows them.
- 6 read
- 5 write
- 22 not documented
What Claude reads (6)
6 toolsSix tools that search and read your workspace, as monday.com describes them.
list_users_and_teams
Fetches data on users, teams or both from your monday.com account.
get_updates
Reads the comment thread posted under an item, with author, timestamps, replies and links to attached files.
list_workspaces
Lists every workspace your account can reach, the top level of how monday.com organizes boards and docs.
get_user_context
Pulls who you are in monday.com along with the boards, folders, workspaces and dashboards that matter to you.
search
Looks for boards, docs, forms and folders across your account, useful when a workspace has grown large.
read_docs
Returns the content of a monday doc as markdown, plain text with light formatting that Claude can quote or summarise.
What Claude can change (5)
5 toolsFive tools that post, file or reorganize content. No source describes a confirmation of their own: the general rule below applies.
create_update
Approval: see the ruleAdds an update to an item, the comment or post that shows under a task for everyone following it.
move_object
Approval: see the ruleMoves folders, boards or overviews to a different place in your account's structure.
create_workspace
Approval: see the ruleCreates a new workspace, the top-level space where a team's boards and docs live.
create_folder
Approval: see the ruleAdds a folder inside a workspace to group boards and docs that belong together.
create_doc
Approval: see the ruleWrites a monday doc from markdown, either inside a workspace or attached to a specific item.
Not documented (22)
22 toolsThe directory lists these names, but monday.com's tool article does not. No official text says what they do, and we will not guess from a name.
create_items_and_tasks
This name sits on the directory sheet, yet monday.com's own tool article, last revised in May 2026, does not list it. No official source describes it, so this page says nothing more about what it does.
create_workflows_and_approvals
Same silence here: no official source describes this name, which appears on the sheet and nowhere in monday.com's tool reference. Better to flag the gap than to fill it with a guess drawn from how the name sounds.
create_dashboards_and_portfolios
Listed by the directory, undocumented by monday.com and by Claude's help pages alike. Nobody publishes what it touches or returns, so its behaviour is unknown and this note stops there on purpose.
create_notifications_and_updates
All we have is a name. The directory publishes it, monday.com's article on its tools does not mention it, and no Claude page explains it. We would rather leave this card short than make something up.
create_forms_and_intake
Absent from the list monday.com publishes, present on Claude's directory sheet, described by no official text. That mismatch is the only fact available, and this page reports it rather than guessing a purpose.
get_board_and_project_status_insights
Neither monday.com nor Anthropic publishes a description of this name. It shows up in the directory's list and in no documentation we could read on 30 September 2026.
update_items_owners_and_status
Nothing official explains this one. The directory sheet carries the name, the monday.com tool article does not, and no help page from Claude fills the gap. This note stays silent on its effect for that reason.
create_boards_and_projects
You will find this name on the directory sheet and not in the tool list monday.com maintains. No source documents it, so any description here would be a guess, and this page does not guess.
get_board_items
Here too the documentation is silent. The monday.com article does not list this name, and no page describes it, so this card says nothing about its effect. The directory sheet, read on 30 September 2026, gives its name and nothing else.
list_automations
No official description exists for this name. monday.com's tool article skips it and Claude's help centre has no page on this connector. What it does stays unknown on this page.
create-sequence
The docs are blank on this one: listed by the directory, missing from monday.com's list, with no wording anywhere about what it involves. The page leaves it undocumented, as the sources do.
get-timeline-items
Only the name is public. No sentence from monday.com or from Anthropic describes it, and its hyphenated spelling differs from the tools monday.com documents. That is all this card can honestly say.
create-timeline-item
There is no wording to go on for this tool. The directory lists it, monday.com's article does not, and no official page gives it a description. Guessing from the name is exactly what this page refuses to do.
manage_agent
Nothing documented, nothing to report. The name appears on Claude's directory sheet only, and no source we read on 30 September 2026 says what it covers or who it acts for.
get_monday_knowledge
Every reference we checked leaves this out: monday.com's tool article, its help pages on the connector, and Claude's documentation. The directory carries the name without a description.
get_assets
A name without a definition. No official source describes it, and the monday.com list does not include it, so this page cannot say what it does or whether it reaches anything sensitive.
update_doc
monday.com's published list does not include this name, and no source describes it. We report the gap and do not match it to another tool by its wording. The directory sheet, read on 30 September 2026, gives its name and nothing else.
all_api_read
No text behind this name either. The directory lists it, and monday.com's tool article never names it. Its reach is unknown, which is a good reason to look at its label in your account's tool settings.
all_api_write
No official source describes this name. monday.com's article does not list it and Claude's documentation does not mention it. Without a description, the default rules are all that applies.
search_meetings_content
No source covers this name: it is missing from monday.com's tool article and from the connector's help pages we read. What it can reach in your account is not published anywhere.
send_feedback
Seen on the sheet, never described. No official source says what this one does, and monday.com's tool article does not name it. The directory sheet, read on 30 September 2026, gives its name and nothing else.
vibe_create
No explanation anywhere for this last name. It is on the directory sheet, not in monday.com's tool article, and not in any Claude documentation. This page will not invent a purpose for it.
What Claude asks you before it acts
By default, Claude stops and asks for your go-ahead before each action it takes on an account for you. The request shows up in the chat, at the moment it matters.
On Team and Enterprise workspaces, owners decide whether members may let some actions through without being asked every time. They can also limit what a connector may do across the whole organization, for example keep reading open and close writing. That setting applies to everyone and nobody overrides it from their own account. And Claude works with your rights and nothing more: monday.com says an assistant acting for you never sees more than you see in its interface, private boards included.
Which plans it is available on
Out of the 819 sheets in the official directory, not one shows availability by plan. The per-connector answer is published nowhere: it is a real hole in the catalogue.
The general rule is published, though. Remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner switches the connector on for the organization before each member can connect. The publisher's own help article says something narrower, which the limits section sets against this rule. For the current state on your account, check the connector's sheet in the official directory.
Where the Claude monday.com connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when an item changes status, a deadline slips or a form comes in.
This page rests on monday.com's own help centre only: no Claude help article covers this connector. The tool list is an observed floor, not a promise, since an admin can open actions that no public sheet shows. The directory's partner badge is not a security audit either, and Anthropic says so on every sheet: it does not pick the tools a publisher exposes and does not vouch that they behave as announced. Connect what comes from a publisher you trust, here monday.com itself. For a connector with a clash between official sources on what it can send, read the Claude gmail connector.
Which Claude plans can use this connector?
- Claude help centre, general connector rule ↗September 2026Remote connectors are open to all users; on Team and Enterprise, an Owner must enable each one first.
- monday.com help article, Connect monday MCP with Claude ↗12 September 2026The publisher states that monday.com is in Claude's directory for users on Pro, Max, Team and Enterprise plans.
What this page followsNeither is stale: Anthropic's rule covers every connector, while monday.com's line targets this one and is therefore more specific. But it is the publisher talking, not Anthropic. Check the directory sheet from your own account before you trust either.
Need help connecting monday.com to Claude?
A person reads every message.
