The monday.com connector.
Boards, items and columns. Connect once with your own key. Every agent your team runs reads the same 6 tools under one permission model.
How access is governed
6
Read tools
Open by default. They run when called, and every call is logged with the endpoint, tool and capability.
0
Write tools
monday.com exposes no write tools. Nothing it does mutates external state.
0
Destructive tools
monday.com defines no destructive tools. Nothing here deletes data.
Defaults come from the capability on each tool definition, and an admin can tighten or open any tool individually. The endpoint's capability ceiling can only tighten that policy. An endpoint scoped to read never surfaces a write tool.
Every monday.com tool
6 tools, named as the agent sees them.
- list_boardsread
List monday.com boards with their item counts. Start here — every other tool needs a board id from this list.
- get_board_structureread
Get one board's columns and groups. Read this before list_board_items or search_board_items — it gives you the column ids those tools filter on, and tells you what each column value means.
- list_board_itemsread
List the items (rows) on a board with all their column values. Use the cursor from a previous call to page forward; note monday rejects cursor and a filter in the same request.
- search_board_itemsread
Find items on a board whose column contains some text. column_id comes from get_board_structure — use "name" to match the item title itself.
- get_itemsread
Get specific items by id, in full and across boards — including their update (comment) threads. Ids come from list_board_items or search_board_items.
- list_usersread
List account users. Use it to turn the person ids inside a column value into names and emails.
Use it from any agent
The same monday.com tools reach Claude Code, Cursor, Claude Desktop or your own agent through one MCP endpoint. The endpoint is scoped to a group, the token is issued per group and revocable from the dashboard, and an allowed-tool list and capability ceiling limit what it exposes. Reads run. Gated writes refuse unless an admin opens them. Destructive tools remain unavailable over MCP.
{
"mcpServers": {
"growth": {
"type": "http",
"url": "https://app.notara.ai/mcp/g/acme/growth",
"headers": {
"Authorization": "Bearer ntr_mcp_xxxxxxxxxxxxxxxxxxxx"
}
}
}
}The URL and token are placeholders. Real endpoints are issued per group from the dashboard.
Setup
- 01
Create a monday.com API Token in your monday.com account (where to find it). The key is yours: Notara stores it encrypted and never sees a bill.
- 02
Paste it into the Notara dashboard. Credentials can be scoped to the workspace or to one person.
- 03
The tools appear with their capability defaults already set. Tighten or open any of them per tool, then invite the agent to a channel or issue an MCP token.
Connect monday.com once. Use it everywhere.
Use Notara directly, or bring us the workflow that needs to be redesigned and built.