Breadth is the obvious part — tasks, boards, comments, todos, documents and dependencies are all here. The design detail worth noticing is time tracking: logging time in Productive needs the right deal and the right service, and these tools name their own order, so an agent walks project, deal, service, task, entry rather than guessing and filing hours against the wrong budget. Read-only tokens are supported, which is a sensible starting point given delete_task and delete_page sit in the same set.
A server over the Productive.io API covering most of the project-management surface: companies and projects, boards, task lists and folders, tasks with subtasks and dependencies, comments and todos, pages and documents, people, workflow statuses, activity feeds and time entries.
- Tasks end to end: listed and filtered, read in detail, created, reassigned, retitled and re-described, moved between lists, repositioned, pushed to the backlog, assigned to sprints and deleted
- Status changes made against real workflow statuses — list_workflow_statuses first, so an update is not a guess at what the board allows
- Boards, task lists and folders with a full lifecycle: create, update, archive, restore, copy from a template, move and reposition
- Subtasks, and typed task dependencies so a blocking relationship is distinguishable from a related one
- Comments treated as first-class: listed, read, added with HTML and @mentions, edited, deleted, pinned, unpinned and reacted to
- Todos — the checklist items on a task — created, updated, listed by status and deleted
- Pages and documents with nested hierarchies: created with an HTML body, updated, moved under another page, copied from a template, deleted
- Time tracking with its ordering made explicit — the project's deals or budgets, then the services on that deal, then the project's tasks, then the entry itself, each tool naming its own step in the sequence
- whoami reports which user ID is configured as "me" and my_tasks returns what is assigned to you; list_activities and get_recent_updates summarise what changed across the organisation over recent days
Published as productive-mcp and launched over stdio with npx, or installed globally. PRODUCTIVE_API_TOKEN and PRODUCTIVE_ORG_ID are required; the token is generated under Settings → API integrations in Productive.io and can be read-only if you only want reads. PRODUCTIVE_USER_ID is optional and is what makes my_tasks and the "me" references resolve.
One command plus a key — npm install -g productive-mcp, then supply credentials