Productive MCP Server

Productive mcp mcp server lets Claude, Cursor and other MCP clients work with Productive MCP directly. MCP server for Productive.io API integration.

What Productive MCP does

An MCP (Model Context Protocol) server that enables Claude Desktop, Claude Code, and other MCP-compatible clients to interact with the Productive.io API.

Key capabilities

• Companies & Projects — List companies and projects with status filtering
• Folders — Full CRUD with archive/restore for organizing project content
• Task Lists — Full lifecycle management — create, update, archive/restore, copy, move, reposition
• Task Management — List, create, update, delete tasks with various filters
• Subtasks — Create and list subtasks under parent tasks
• Task Operations — Comments, status updates, sprint assignment, repositioning
• Comments — Full CRUD with pin/unpin and reactions
• Todos — Checklist items on tasks — create, update, close/reopen, delete

Tools it exposes

Once connected, the assistant can call these 14 tools directly:

• macOS — ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows — %APPDATA%\Claude\claude_desktop_config.json
• whoami — Get current user context and configured user ID
• list_companies — List companies/customers. Filter by status (active/archived), limit
• list_projects — List projects. Filter by status, company_id, limit
• list_folders — List folders in a project. Filter by project_id, status (1=active, 2=archived), limit
• get_folder — Get folder details by folder_id
• create_folder — Create a folder. Requires project_id, name
• update_folder — Rename a folder. Requires folder_id, optional name
• archive_folder — Archive a folder by folder_id
• restore_folder — Restore an archived folder by folder_id
• list_boards — List boards. Filter by project_id, limit
• create_board — Create a board. Requires project_id, name
• list_task_lists — List task lists. Filter by board_id, limit

Installing the productive mcp mcp server

The server is distributed via npm as productive-mcp, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply 3 environment variables: PRODUCTIVE_API_TOKEN, PRODUCTIVE_ORG_ID, PRODUCTIVE_USER_ID. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Productivity servers pay off through capture: the tasks and notes that never get filed are the ones where opening the app is more friction than the thought is worth. Productive MCP sits in that group, and the shape of its toolset — macOS, Windows, whoami among others — tells you what it is really for. Worth comparing against the other productivity servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• With 14 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Productive MCP.
• Maintained by berwickgeek, written in Go.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the productive mcp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.