Connect Claude to your actual tasks.
Planrotfish ships an MCP server, so an AI assistant can work with your real plan instead of a description of it — list what’s open, file new work, re-prioritise a backlog, move cards across the board. You grant access with an OAuth consent screen and revoke it whenever you like.
Why this is different from pasting your to-do list into a chat
An assistant working from pasted text is working from a snapshot that was already stale when you copied it, and anything it decides stays in the conversation. Over MCP it reads the database directly and writes back to it, so “move everything I finished into done and schedule the rest across next week” is one instruction that changes the real board.
Because the connection acts as you, the same row-level security that protects the app applies unchanged. There is no service account with broad access sitting in the middle, and nothing is visible to the assistant that wouldn’t be visible to you.
What Claude can do
- list_workspaces — Every workspace the connected account belongs to.
- list_projects — Projects inside a workspace, with their boards.
- list_tasks — Tasks, filtered by project, board column, schedule or status.
- create_task — File new work — title, detail, priority, estimate, due date.
- update_task — Change any field, including marking something finished.
- move_task — Move a card between board columns, or onto a day.
- archive_task — Archive work that's no longer relevant.
- list_board_columns — The lanes a project's board is made of.
- list_members — Who's in the workspace, for assignment.
Connecting it
- Create an account and a workspace
The connector authorises against a real account, so there has to be one. Pro is $4.99 per month, one plan with everything included.
- Add the connector in Claude
In Claude’s settings, add a custom connector and give it the Planrotfish endpoint:
https://planrotfish.com/api/mcp - Approve the connection
Claude opens a Planrotfish consent screen. Approve it and the tools appear in the conversation. Revoke it any time from Settings → MCP — no password ever changes hands.
Things worth asking it
- “What’s overdue across all my projects, and what should I do first?”
- “Turn these meeting notes into tasks in the Backend project, with owners.”
- “Spread everything unscheduled across next week, avoiding my meeting blocks.”
- “Move everything in review that I’ve approved into done.”
Questions
What is an MCP server?
MCP — the Model Context Protocol — is an open standard that lets an AI assistant call a real application's functions instead of guessing from text you paste in. A Planrotfish MCP connection gives Claude direct, permissioned access to your actual tasks, so what it tells you is what the app contains.
Does Claude get access to my whole account?
It gets exactly the nine tools listed above, acting as you, scoped by the same row-level security that governs the app itself. You approve the connection on an OAuth consent screen and can revoke it at any time from Settings. No password is ever shared with the assistant.
Which MCP clients work with it?
Any client that speaks MCP over streamable HTTP with OAuth 2.1, which includes Claude on the web as a custom connector and Claude Desktop. The endpoint is a normal remote MCP server, so nothing needs installing locally.
Can Claude change things, or only read them?
Both. Reading is the safe half — asking what's due this week, what's stuck in review. Writing is where it earns its place: filing follow-ups from a meeting, re-prioritising a backlog, moving finished work across the board, all in one instruction.
What does it cost?
MCP access is part of the single Pro plan at $4.99 per month — there is no separate AI add-on and no per-seat pricing for it. Cancel any time; your data stays readable.