monday.com MCP — Сценарии использования, Установка & Живое демо

Зачем использовать

Ключевые функции

Board, group, item, column, and subitem CRUD
Posts updates (comments) on items for audit trail
Filter items by column values for reporting
Creates webhooks (if you need push → Claude)
Handles monday's quirky column-value JSON so you don't have to

Живое демо

Как выглядит на практике

monday.replay ▶ готово

0/0

Установка

Выберите клиент

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "monday": {
      "command": "npx",
      "args": [
        "-y",
        "@mondaydotcomorg/monday-api-mcp"
      ]
    }
  }
}

Откройте Claude Desktop → Settings → Developer → Edit Config. Перезапустите после сохранения.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "monday": {
      "command": "npx",
      "args": [
        "-y",
        "@mondaydotcomorg/monday-api-mcp"
      ]
    }
  }
}

Cursor использует ту же схему mcpServers, что и Claude Desktop. Конфиг проекта приоритетнее глобального.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "monday": {
      "command": "npx",
      "args": [
        "-y",
        "@mondaydotcomorg/monday-api-mcp"
      ]
    }
  }
}

Щёлкните значок MCP Servers на боковой панели Cline, затем "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "monday": {
      "command": "npx",
      "args": [
        "-y",
        "@mondaydotcomorg/monday-api-mcp"
      ]
    }
  }
}

Тот же формат, что и Claude Desktop. Перезапустите Windsurf для применения.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "monday",
      "command": "npx",
      "args": [
        "-y",
        "@mondaydotcomorg/monday-api-mcp"
      ]
    }
  ]
}

Continue использует массив объектов серверов, а не map.

~/.config/zed/settings.json

{
  "context_servers": {
    "monday": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "@mondaydotcomorg/monday-api-mcp"
        ]
      }
    }
  }
}

Добавьте в context_servers. Zed перезагружается автоматически.

claude mcp add monday -- npx -y @mondaydotcomorg/monday-api-mcp

Однострочная команда. Проверить: claude mcp list. Удалить: claude mcp remove.

Сценарии использования

Реальные сценарии: monday.com

Auto-generate a daily standup digest from a project board

👤 Team leads running standups on monday.com ⏱ ~15 min beginner

Когда использовать: You want 'what moved yesterday, what's blocked, what's due today' without hand-scrolling the board.

Предварительные требования

monday API token — monday.com → avatar → Developers → My Access Tokens
Board ID — URL contains /boards/<board_id>

Поток

Pull items updated in last 24h

List items on board <id> where updated_at > yesterday. Show name, status, owner, due date.✓ Скопировано

→ Recent-activity list
Segment by status

Group these by status column value: Done / Working / Stuck / To Do. Show counts and who owns each Stuck item.✓ Скопировано

→ Clear 4-bucket summary
Format the standup

Format a 10-line standup: moved-to-Done (count), started-Working (count), Stuck items with owner @-mentions, items due today.✓ Скопировано

→ Copy-pasteable digest

Итог: A standup digest you can paste into Slack or LINE in 30 seconds.

Подводные камни

Filtering by updated_at includes column-value changes AND subitem updates — noisy — Add an activity_logs query filtered to status or owner changes only

Сочетать с: line-bot · ms-teams

Bulk-import 500 items into a board from a CSV

👤 PMs kicking off a new project with pre-listed tasks ⏱ ~25 min intermediate

Когда использовать: You have a Google Sheet / CSV of tasks and want them on a monday board with the right columns filled in.

Предварительные требования

CSV with columns matching the board — Header names should roughly match the board columns: name, status, owner_email, date

Поток

Inspect target board schema

Describe board <id>: every column with its id, title, type, and allowed values.✓ Скопировано

→ Column catalog
Map CSV to column_values

Given my CSV headers [paste], produce a mapping to monday column ids. Flag any CSV rows with statuses not in the allowed set.✓ Скопировано

→ Mapping + validation report
Create items in batches

Create these items in batches of 25 with create_item + the mapped column_values. Stop if 3 consecutive calls fail.✓ Скопировано

→ All itemIds; any failures listed with row numbers

Итог: All 500 items on the board with owner, status, and due date pre-filled.

Подводные камни

Column-value JSON shape differs per column type — easy to send invalid payload — Always fetch the column type first; status uses {label:'...'}, date uses {date:'YYYY-MM-DD'}, people uses {personsAndTeams:[{id,kind}]}
Rate limits kick in at ~60 items/min — Sleep between batches; monday returns 429 that the MCP surfaces — add a 2s pause

Сочетать с: filesystem

Post an AI-written status update on every active item

👤 Ops/PMO wanting written context on every in-flight item ⏱ ~30 min intermediate

Когда использовать: End of week — you want every 'Working on it' item to get a 2-line status update automatically.

Поток

Find active items

List items on board <id> where status = 'Working on it'. Include name, owner, last update text.✓ Скопировано

→ In-flight items
Draft a 2-line update per item

For each item, draft a 2-sentence status update based on the last_update + recent column changes. Use a neutral tone.✓ Скопировано

→ Drafts ready for review
Post after approval

Show me drafts 3 at a time. On my 'ok', post as an update on the item.✓ Скопировано

→ Updates posted; itemIds confirmed

Итог: Every active item now has a fresh end-of-week note, no busy-work for the team.

Подводные камни

Auto-posting without review can embarrass you (wrong context) — Always gate posts behind human 'ok' for at least the first week

Сочетать с: github

Generate an exec portfolio rollup across 10 project boards

👤 Program managers / chiefs of staff ⏱ ~30 min advanced

Когда использовать: Weekly leadership review: one slide summarizing health of every project.

Поток

Enumerate portfolio

List boards in folder 'Engineering / Projects'. For each, count items by status.✓ Скопировано

→ Per-board status distribution
Compute a health score

For each board: health = 100 - 5*(stuck items) - 2*(overdue items). Flag < 70 as red.✓ Скопировано

→ Board → health + color
Produce a markdown report

Generate a one-screen markdown table: Board | Health | Stuck | Overdue | Top risk. Order by health ascending.✓ Скопировано

→ Leadership-ready table

Итог: An at-a-glance portfolio dashboard, repeatable weekly.

Подводные камни

'Stuck' and 'overdue' meanings vary across boards — Standardize status columns or keep per-board overrides in a config file

Сочетать с: notion

Find and archive stale items across a board

👤 Board owners tired of cruft ⏱ ~25 min intermediate

Когда использовать: Board has grown to 1000+ items with many untouched for months.

Поток

Find untouched items

Items on board <id> not updated in 90+ days and status != Done. List name, owner, last update date.✓ Скопировано

→ Stale list
Decide per-item

Show the list 10 at a time. For each: keep / archive / reassign. I'll say one letter per item.✓ Скопировано

→ Triage decisions
Execute archive/move

Apply: archive the 'a' items with archive_item, reassign 'r' items to owner <me>, keep 'k'.✓ Скопировано

→ Board cleaned; change log saved

Итог: A board that reflects reality, with an audit log of what was archived and why.

Подводные камни

Archived items are invisible; hard to restore if you regret it later — Duplicate the board first as a snapshot, OR use labels instead of archive for a trial run

Create an incident item with linked artifacts after a Sentry page

👤 On-call engineers ⏱ ~15 min intermediate

Когда использовать: Incident just closed; you want a monday item capturing scope, timeline, and owners.

Поток

Collect the artifacts

From Sentry, get issue <id>: title, first seen, users affected, resolving release. From GitHub, the PR that fixed it.✓ Скопировано

→ Artifact bundle
Create the monday item

On board 'Incidents', create_item with name='<Sentry title>', status='Resolved', owner=me, date=today, description=auto-written postmortem including artifact links.✓ Скопировано

→ itemId returned
Post the timeline as an update

Post a timeline update on that item: detection time, deploy reverted at, root cause, followups.✓ Скопировано

→ Update posted

Итог: A postmortem item created within 5 minutes of incident close, with everything linked.

Подводные камни

Over-long description breaks monday formatting — Keep description to headlines; put details in a threaded update

Сочетать с: sentry · github

Комбинации

Сочетайте с другими MCP — эффект x10

monday + sentry

Auto-create a monday incident item when a critical Sentry issue fires

When Sentry issue WEB-3a91 reaches 100+ events, create an item on board 'Incidents' with name=issue title and severity column set to P1.✓ Скопировано

monday + github

Link a PR merge to a monday item status change

When PR #342 merges, find monday item matching its title and set status to 'Done'.✓ Скопировано

monday + notion

Weekly exec portfolio rollup posted to Notion

Run the portfolio health rollup and create a Notion page with the result as a table.✓ Скопировано

Инструменты

Что предоставляет этот MCP

Инструмент	Входные данные	Когда вызывать	Стоимость
list_boards	workspace_id?, limit?	Discover boards	GraphQL complexity units
get_board	board_id	Inspect schema before writes	complexity
list_items	board_id, limit?, cursor?, columns_filter?	Paged item fetch	complexity
create_item	board_id, group_id?, name, column_values?	Add a new task	complexity
change_column_value	board_id, item_id, column_id, value	Update status, owner, date, etc.	complexity
create_update	item_id, body	Post a comment on an item	complexity
archive_item	item_id	Remove without deleting	complexity
create_webhook	board_id, url, event	Push changes to an external system	complexity

Стоимость и лимиты

Во что обходится

Квота API: Complexity-budget limits: 10M complexity/minute on Pro; 5M on Standard. Heavy queries cost more.
Токенов на вызов: Item reads: 500–2000 tokens. Board schema: 500–1500 tokens.
Деньги: API is free at your plan level. monday plans start at ~$9/user/mo.
Совет: Use columns filter in list_items to return only the fields you need — avoids hitting complexity cap on wide boards.

Безопасность

Права, секреты, радиус поражения

Минимальные скоупы: me:read boards:read

Хранение учётных данных: MONDAY_API_TOKEN (personal token) in env

Исходящий трафик: All calls to api.monday.com

Никогда не давайте: account:admin for an MCP that only reads specific boards

Personal tokens inherit YOUR permissions across every board you can see — scope tightly.
Use OAuth app with requested scopes when shipping this to end users.

Устранение неполадок

Частые ошибки и исправления

401 Not Authenticated

MONDAY_API_TOKEN missing/expired. Regenerate at monday.com → Developers → My Access Tokens.

Проверить: curl -H 'Authorization: $MONDAY_API_TOKEN' https://api.monday.com/v2 -d '{"query":"{ me { name } }"}'

ComplexityException — Max complexity reached

Query too heavy. Reduce limit or fetch fewer columns/subitems per item.

ColumnValueException — invalid column value

Column-value JSON shape wrong for the column type. Fetch the column first and inspect the type, then build the JSON accordingly (status: {label}, date: {date:'YYYY-MM-DD'}).

Rate limit exceeded (429)

Back off to ~1 write/sec. monday enforces per-minute throttles on mutations.

Альтернативы

monday.com в сравнении

Альтернатива	Когда использовать	Компромисс
Linear MCP	Engineering-focused teams want keyboard-first issue tracking	Less flexible than monday; no arbitrary column types
Asana MCP	Team is on Asana	Different column/field model
Notion MCP	You want docs + light tracking in one surface	Weaker at dense project management; not a real PM tool

Ещё

Ресурсы

📖 Читать официальный README на GitHub

🐙 Открытые задачи

🔍 Все 400+ MCP-серверов и Skills