monday.com MCP — Casos de uso, Instalar & Demo ao vivo

Por que usar

Principais recursos

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

Demo ao vivo

Como fica na prática

monday.replay ▶ pronto

0/0

Instalar

Escolha seu cliente

~/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"
      ]
    }
  }
}

Abra Claude Desktop → Settings → Developer → Edit Config. Reinicie após salvar.

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

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

Cursor usa o mesmo esquema mcpServers que o Claude Desktop. Config de projeto vence a global.

VS Code → Cline → MCP Servers → Edit

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

Clique no ícone MCP Servers na barra lateral do Cline, depois "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

Mesmo formato do Claude Desktop. Reinicie o Windsurf para aplicar.

~/.continue/config.json

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

O Continue usa um array de objetos de servidor em vez de um map.

~/.config/zed/settings.json

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

Adicione em context_servers. Zed recarrega automaticamente ao salvar.

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

Uma linha só. Verifique com claude mcp list. Remova com claude mcp remove.

Casos de uso

Usos do mundo real: monday.com

Auto-generate a daily standup digest from a project board

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

Quando usar: You want 'what moved yesterday, what's blocked, what's due today' without hand-scrolling the board.

Pré-requisitos

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

Fluxo

Pull items updated in last 24h

List items on board <id> where updated_at > yesterday. Show name, status, owner, due date.✓ Copiado

→ 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.✓ Copiado

→ 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.✓ Copiado

→ Copy-pasteable digest

Resultado: A standup digest you can paste into Slack or LINE in 30 seconds.

Armadilhas

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

Combine com: 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

Quando usar: You have a Google Sheet / CSV of tasks and want them on a monday board with the right columns filled in.

Pré-requisitos

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

Fluxo

Inspect target board schema

Describe board <id>: every column with its id, title, type, and allowed values.✓ Copiado

→ 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.✓ Copiado

→ 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.✓ Copiado

→ All itemIds; any failures listed with row numbers

Resultado: All 500 items on the board with owner, status, and due date pre-filled.

Armadilhas

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

Combine com: filesystem

Post an AI-written status update on every active item

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

Quando usar: End of week — you want every 'Working on it' item to get a 2-line status update automatically.

Fluxo

Find active items

List items on board <id> where status = 'Working on it'. Include name, owner, last update text.✓ Copiado

→ 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.✓ Copiado

→ Drafts ready for review
Post after approval

Show me drafts 3 at a time. On my 'ok', post as an update on the item.✓ Copiado

→ Updates posted; itemIds confirmed

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

Armadilhas

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

Combine com: github

Generate an exec portfolio rollup across 10 project boards

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

Quando usar: Weekly leadership review: one slide summarizing health of every project.

Fluxo

Enumerate portfolio

List boards in folder 'Engineering / Projects'. For each, count items by status.✓ Copiado

→ Per-board status distribution
Compute a health score

For each board: health = 100 - 5*(stuck items) - 2*(overdue items). Flag < 70 as red.✓ Copiado

→ Board → health + color
Produce a markdown report

Generate a one-screen markdown table: Board | Health | Stuck | Overdue | Top risk. Order by health ascending.✓ Copiado

→ Leadership-ready table

Resultado: An at-a-glance portfolio dashboard, repeatable weekly.

Armadilhas

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

Combine com: notion

Find and archive stale items across a board

👤 Board owners tired of cruft ⏱ ~25 min intermediate

Quando usar: Board has grown to 1000+ items with many untouched for months.

Fluxo

Find untouched items

Items on board <id> not updated in 90+ days and status != Done. List name, owner, last update date.✓ Copiado

→ Stale list
Decide per-item

Show the list 10 at a time. For each: keep / archive / reassign. I'll say one letter per item.✓ Copiado

→ Triage decisions
Execute archive/move

Apply: archive the 'a' items with archive_item, reassign 'r' items to owner <me>, keep 'k'.✓ Copiado

→ Board cleaned; change log saved

Resultado: A board that reflects reality, with an audit log of what was archived and why.

Armadilhas

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

Quando usar: Incident just closed; you want a monday item capturing scope, timeline, and owners.

Fluxo

Collect the artifacts

From Sentry, get issue <id>: title, first seen, users affected, resolving release. From GitHub, the PR that fixed it.✓ Copiado

→ 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.✓ Copiado

→ itemId returned
Post the timeline as an update

Post a timeline update on that item: detection time, deploy reverted at, root cause, followups.✓ Copiado

→ Update posted

Resultado: A postmortem item created within 5 minutes of incident close, with everything linked.

Armadilhas

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

Combine com: sentry · github

Combinações

Combine com outros MCPs para 10× de alavancagem

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.✓ Copiado

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'.✓ Copiado

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.✓ Copiado

Ferramentas

O que este MCP expõe

Ferramenta	Entradas	Quando chamar	Custo
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

Custo e limites

O que custa rodar

Cota de API: Complexity-budget limits: 10M complexity/minute on Pro; 5M on Standard. Heavy queries cost more.
Tokens por chamada: Item reads: 500–2000 tokens. Board schema: 500–1500 tokens.
Monetário: API is free at your plan level. monday plans start at ~$9/user/mo.
Dica: Use columns filter in list_items to return only the fields you need — avoids hitting complexity cap on wide boards.

Segurança

Permissões, segredos, alcance

Escopos mínimos: me:read boards:read

Armazenamento de credenciais: MONDAY_API_TOKEN (personal token) in env

Saída de dados: All calls to api.monday.com

Nunca conceda: 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.

Solução de problemas

Erros comuns e correções

401 Not Authenticated

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

Verificar: 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.

Alternativas

monday.com vs. outros

Alternativa	Quando usar	Troca
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

Mais

Recursos

📖 Leia o README oficial no GitHub

🐙 Ver issues abertas

🔍 Ver todos os 400+ servidores MCP e Skills