Rather than one tool per create, update and delete, each object type gets a single manage tool with an action argument — twelve write tools against thirty-five read tools. That keeps the write surface reviewable and makes it obvious in a transcript when something was changed. The agent skills are the other unusual piece: the customer-facing one deliberately omits internal ids, lane names and OKRs, so a roadmap can be discussed with a customer without leaking the internals.
A Go MCP server over the ProductPlan API, shipped as a single binary. It splits its surface deliberately: 35 read tools that fetch, and 12 action-based write tools that take an action argument, so creating and editing go through a smaller, more deliberate set.
- Roadmap reads: list roadmaps, open one, and pull its bars, lanes, milestones, legends and comments — or the whole thing at once — `list_roadmaps`, `get_roadmap`, `get_roadmap_bars`, `get_roadmap_lanes`, `get_roadmap_milestones`, `get_roadmap_complete`
- Bar detail including children, comments, connections and links — `get_bar`, `get_bar_children`, `get_bar_connections`, `get_bar_links`
- OKRs: objectives and key results, read and managed — `list_objectives`, `get_objective`, `list_key_results`, `manage_objective`, `manage_key_result`
- Discovery: ideas, opportunities, idea forms, and the customers and tags attached to them — `list_ideas`, `get_idea`, `list_opportunities`, `list_all_customers`, `list_all_tags`, `manage_idea`, `manage_opportunity`
- Launches with their sections and tasks — `list_launches`, `get_launch_sections`, `get_launch_tasks`, `manage_launch`, `manage_launch_section`, `manage_launch_task`
- Roadmap writes through action-based tools covering create, update and delete — `manage_bar`, `manage_lane`, `manage_milestone`, `manage_bar_connection`, `manage_bar_link`
- Admin and health reads, plus users and teams — `check_status`, `health_check`, `list_users`, `list_teams`
- Pre-built agent skills for different audiences — a general workflow reference, a PM toolkit, a leadership view and a customer-facing one that omits internal ids and OKRs
- A CLI over the same binary: `productplan roadmaps`, `productplan objectives`, `productplan ideas`, `productplan launches`
A ProductPlan API token from Settings > API, supplied as `PRODUCTPLAN_API_TOKEN` — required, and it only reaches data your account can see. Download the binary for your platform from the releases page, make it executable and put it on your path, then reference it by full path in the client config; on Windows use double backslashes in JSON. A container image `ghcr.io/olgasafonova/productplan-mcp-server` is published at 4.8.2, and `.mcpb` bundles exist for macOS, Linux and Windows. Setup pages are supplied for Claude Desktop, Claude Code, Cursor, VS Code with Cline or Continue, and n8n. The token never leaves your machine — the client spawns the binary and talks over stdin and stdout.
Build from source — clone the repository and build it, then point your client at the binary