Overdue tasks chased before the client asks

An agent that scans monday.com boards each morning for items past their due date, posts a nudge on each item and sends the project lead one summary

The problem

Due dates on a monday.com board turn red quietly, and the project lead finds out when the client asks where the deliverable is. Chasing by hand means opening every board, scrolling for red dates and writing the same polite reminder ten times.

How the agent works

1. It starts

   com MCP server connected through a read and write token scoped to the project workspace.

2. The agent works

   It reads every item on the boards listed in its prompt, keeps those whose Due date column is before today and whose Status is not Done or Cancelled, and groups them by owner. com's own notification, and it writes one summary for the project lead in Slack or Teams, sorted by how late each item is, with a flag on anything the client can see. The lead replies with the items to pause and the agent remembers them so nobody is nagged twice for a date that was already renegotiated.

3. The result

   The agent never changes a due date or a status; those stay with the people on the board.

Worked example

monday.com's open source MCP server exposes get_board_items_by_name, create_update and change_item_column_values, with a --read-only flag for testing and a hosted version at mcp.monday.com that signs in with OAuth; monday's official Python SDK shows the same building blocks (fetch_all_items_by_board_id, create_update, change_date_column_value). Claude Code routines run on a schedule from Anthropic's cloud with connectors attached, hourly to weekly, so the nudge needs no server of its own. Neither page reports how many overdue items a team cleared; count red dates per board for a month before and after you switch it on.

Sources

• https://github.com/mondaycom/mcp
• https://github.com/mondaycom/monday-api-python-sdk
• https://code.claude.com/docs/en/routines