ProductPlan MCP server
ProductPlan in any MCP client, through Memtro: ProductPlan does not publish this server. Memtro's ProductPlan connector reads ProductPlan through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
ProductPlan roadmaps: roadmaps, their bars (planned items) with lane, legend, dates, progress, tags and description, a bar's comments, discovery ideas and opportunities, objectives with key results, launches with their tasks, and teams. When you ask, can create, edit or delete a bar, add a milestone, create or edit ideas, opportunities and objectives, delete an objective, add or update a key result, create a launch, and update a launch task.
Reads
productplan_list_roadmapsProductPlan roadmaps you can see: id, name, description, your permission, lanes and legends, last update.productplan_list_barsBars (planned items) on one ProductPlan roadmap: name, lane, legend, start and end dates, percent done, parked, container, tags, short description.productplan_get_barOne ProductPlan bar in full (description, strategic value, notes, custom fields, parent) with its comments (text and time; authors are not named).productplan_list_ideasProductPlan discovery ideas: name, description, channel, customer, linked opportunity count, tags, teams, visible or archived.productplan_list_opportunitiesProductPlan discovery opportunities: problem statement, workflow status (draft, in discovery, validated, invalidated, completed), description…productplan_list_objectivesProductPlan objectives: name, description, risk status, active or archived, dates, key result, bar and opportunity counts.productplan_list_launchesProductPlan launches: name, description, launch date, status (low, medium or high risk, launched), progress, owner id, bar and task counts.productplan_list_teamsProductPlan teams: id and name, for the team_ids the idea, opportunity, objective and launch tools take.
Acts, when you ask
These change something in ProductPlan. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
productplan_create_barAdds a bar (planned item) to a ProductPlan roadmap, visible to everyone who can see it.productplan_update_barChanges a ProductPlan bar: name, dates, lane, legend, progress, tags (replaced), description, notes, parked, or container.productplan_delete_barPermanently deletes a ProductPlan bar from its roadmap, for everyone.productplan_create_milestoneAdds a milestone (a dated marker) to a ProductPlan roadmap, optionally in one lane.productplan_create_ideaRecords an idea in ProductPlan discovery.productplan_update_ideaChanges a ProductPlan idea: name, description, customer, tags or links (each list replaces the old one), or archives it (location_status archived).productplan_create_opportunityCreates a discovery opportunity in ProductPlan from a problem statement, optionally linked to ideas, bars, objectives and teams.productplan_update_opportunityChanges a ProductPlan opportunity: problem statement, description, workflow status, owner, links (each list replaces the old one), or archives it.productplan_create_objectiveCreates an objective in ProductPlan strategy, optionally with dates, risk status, teams and linked opportunities.productplan_update_objectiveChanges a ProductPlan objective: name, description, risk status, dates, teams or opportunities (lists replace), or archives it…productplan_delete_objectivePermanently deletes a ProductPlan objective with its key results, for everyone.productplan_create_key_resultAdds a key result to a ProductPlan objective, with a start and target value and a type (percent, money or number).productplan_update_key_resultUpdates a ProductPlan key result, most often its current value, or its description, start, target or type.productplan_create_launchCreates a launch in ProductPlan with a launch date (YYYY-MM-DD), status and optional linked bars and teams.productplan_update_launch_taskChanges a task on a ProductPlan launch: status (to do, in progress, completed, blocked), name, description, due date, checklist section, or assignee…
Connect it
First connect ProductPlan on Dashboard → Connections, then add Memtro to your client once. The ProductPlan tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared ProductPlan connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › Which bars on the mobile roadmap end this month?
- › Which opportunities are still in discovery?
- › How are the key results on our retention objective tracking?
- › Which launch tasks are blocked?
- › What ideas have come from customers recently?
Questions
- Is this an official ProductPlan MCP server?
- No. It is Memtro's MCP server with Memtro's ProductPlan connector behind it: the connector reads ProductPlan through its API with the credentials you connect on Dashboard → Connections, and ProductPlan publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in ProductPlan?
- Only when you ask, and only what it has been granted: create a roadmap bar; edit, move, park or unpark a bar; delete a bar; add a milestone to a roadmap; create an idea; edit or archive an idea; create an opportunity; edit, re-status or archive an opportunity; create an objective; edit or archive an objective; delete an objective; add a key result to an objective; update a key result's values; create a launch; update a launch task's status, owner or due date. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.