Cursor

Cursor supports MCP servers, so the task list you are working from is available in the same window as the diff.

Step 1: Add the connector

Add a new MCP server in Cursor's settings with https://mcp.cretask.com/mcp as its URL, then complete the sign-in Cretask prompts for. The connector is per-account, so each person on the team authorizes their own.

Step 2: Choose what it can reach

Cretask's authorization screen lists exactly what is being asked for: reading tasks and projects, creating and updating them, and adding notes. Read-only is a real choice if you only want Cursor to summarise your week. The grant can be narrowed or revoked at any time from Settings, Security, and the connector stops working the moment you do.

Step 3: Work in plain language

Ask for what you would ask a person. What am I meant to be doing on this project today. Close the task about the offline sync retry and note what fixed it. Cursor resolves names, dates and projects against your live workspace rather than guessing at them, and tells you what it changed.

Step 4: Keep an audit trail

Every write is stamped with the actor, so a task Cursor created is visibly a task Cursor created, on the board and in the task's own history. Batched changes undo as one unit for thirty days, which is what makes it safe to hand over bulk work. Watch the first few runs, then let it run.

Start getting things done

Bring every task, project and plan into one place, and let Claude do the busywork alongside you.