Stack: Claude (web/desktop) + monday.com MCP connector

What this actually does

You inherited a board. Nobody knows what half the columns mean, the status column has fourteen labels including "Done", "done", "Complete" and "Closed — DO NOT USE", forty items have no owner, and the last person who understood it left in March.

This tutorial uses Claude as a diagnostic and remediation engine against monday's API. Claude reads the whole board, measures the mess numerically, proposes a clean-up plan, and — after you approve it — executes the writes in batches.

What it does not do: it does not know what your team meant. Claude will produce a confident, plausible taxonomy that may be wrong for your org. Every write phase in this tutorial has a human approval gate for that reason. Treat Claude as a very fast analyst with no institutional memory, because that is exactly what it is.

0. Before you touch anything

0.1 Connect and confirm scope

Enable the monday.com connector in Claude, then run:

Call get_user_context. Tell me who I'm authenticated as and what my account plan is.

Then confirm you can actually write:

Call get_board_info for board <BOARD_ID> with filters.columns.only: true. Confirm the board name and tell me whether I have permission to change board structure.

Failure mode to catch here: you inherited the board but were never made an owner. Reads will succeed and writes will fail halfway through a batch, leaving you in a partially-migrated state. Fix permissions first.

0.2 Take a snapshot

A single mistaken action can sometimes be reversed with the undo_action mutation, which takes a job_id you get from get_board_activity with includeData: true. Do not rely on it for a bulk write — treat a duplicate of the board as your real rollback plan.

Use all_api_write to run the duplicate_board mutation on board <BOARD_ID> with duplicate_type: duplicate_board_with_pulses_and_updates, into the same workspace, named <BOARD_NAME> — PRE-CLEANUP SNAPSHOT <DATE>.

Use that exact duplicate type. The alternatives — duplicate_board_with_pulses and duplicate_board_with_structure — discard the update history, which is the audit's truest staleness signal.

Confirm the snapshot has the same item count as the original before you continue. If it doesn't, stop.

0.3 Set the ground rule