How to
How to connect Claude to monday.com
Monday.com's directory connector lets Claude look at your boards. The work, though, is not looking at boards. It is creating the item, setting the status, moving it between groups, and posting the update, and that is where a thin API slice runs out.
Connect Claude to monday.com either with the directory connector, which tends to be read-leaning and lets Claude look up boards and items, or with a custom MCP connector when you need reliable writes. A custom build lets Claude create items, update column values, move items between groups, and post updates, with destructive actions gated behind your approval.
Key takeaways
- Monday.com's directory connector tends to be read-leaning or covers a thin slice of the API: Claude can often look up boards and items but cannot reliably create items, update columns, or post updates.
- A custom connector adds write tools like `create_item`, `update_column`, and `post_update`, so Claude works directly on the board.
- It authenticates as your monday.com account through OAuth, so Claude can only see and change the boards you already can.
- Destructive actions like deleting an item or archiving a board are gated write tools that run only after you approve them.
Does monday.com have a Claude connector already?
There is a monday.com connector in the directory, but it tends to be read-leaning or to cover a thin slice of the API. In practice, Claude can often look up boards and items, but reliably creating items, updating column values, and posting updates falls outside what it ships.
Start with the honest version: if what you want is Claude answering questions about what is on your boards, the directory connector may cover that. Ask what is stuck, what is due this week, or who owns what, and Claude can read the answer off the board.
The friction is that board maintenance is the actual chore. Standup notes need to become items, statuses need to move when the work moves, and context needs to land as an update on the right item. When the connector cannot write reliably, all of that stays manual clicking, with Claude narrating from the sidelines.
The wider pattern holds beyond this one tool: in our June 2026 review of 264 business tools, 77 percent had no Claude connector at all, and none shipped full read-write out of the box.
How do I set up a custom monday.com connector for Claude?
A custom monday.com connector is built for you as a small MCP server that authenticates with OAuth and the narrowest scopes the work needs. Read tools and write tools are separated, Claude acts as your own monday.com account, and destructive actions like deleting an item wait for your confirmation.
The path from request to working connector:
- 1Describe the monday.com work Claude should handle: the boards it maintains, the columns that matter, the workflow your groups represent.
- 2We build a small MCP server with read tools (search boards, read items) separated from write tools (create item, update column, post update).
- 3You authenticate through OAuth as your own monday.com account, so Claude inherits your existing permissions and board access.
- 4Claude starts creating items and moving work forward in conversation, with destructive actions like deleting an item gated behind your approval.
Access is revocable at any time, and scopes are kept to what the work needs.
What can Claude do in monday.com with write access?
With full read-write access, Claude creates a new item on the right board and populates its columns, updates statuses and dates on existing items, moves items between groups as work progresses, posts updates to capture context, assigns owners, and creates subitems after you approve.
The tool set maps to the board maintenance most teams still click through by hand:
create_itemto create a new item on a board and populate its columns.update_columnto update a status, date, or other column value on an existing item.move_itemto move an item between groups as it progresses through a workflow.post_updateto post an update or comment on an item to capture context.assign_ownerto assign an owner or set a person column on an item.
Claude can also create a subitem under a parent item after you approve, so breaking a task down happens in the conversation where the task came up.
Will Claude delete items or change my boards without asking?
No. Destructive actions like deleting an item or archiving a board are separate, gated write tools that only run after you approve them. Routine edits like status changes can be set to run directly, while anything irreversible waits for a confirmation step. You decide which is which.
In practice, most teams let board reads and status updates flow freely, keep item creation and updates fast, and reserve confirmations for deletes, archives, and anything that touches a board the whole company sees. The line is yours to draw.
Claude only has your access
The connector authenticates as your account through OAuth and inherits your existing permissions, so it can only see and change the boards you already can. It never grants Claude more access to your monday.com workspace than you have yourself, and you can revoke it at any time.
When is the directory monday.com connector enough, and when is it not?
The directory connector is enough when your work is reading: what is on the board, what is late, who owns what. It stops being enough when Claude should change the board: creating items, setting statuses, moving work between groups, and posting updates need reliable write tools, and that means a custom connector.
A quick self-test: write down the last five things you wished Claude had done in monday.com. If they are all questions answered by looking at a board, the directory connector may cover you. If any end with an item created, a status changed, or an update posted, a read-leaning connector will not carry them, and a purpose-built one with scoped writes will.