
Autopm
io.github.fluidumberPublished by GitHub account fluidumberv4.0.1Updated Oct 24, 2026
18 AI product-management robots for market research, financials, and execution specs. No API keys
Overview
AutoPM is a local MCP server that runs a pipeline of AI product-management agents to turn a business idea into a validated product strategy and pitch deck.
- What you can do
- Run a gated two-phase product workflow: strategic discovery first, then execution definition.
- Interview the user to lock in the product idea, then run individual robots for market sizing, competitive intelligence, personas, financial projections, feature breakdown, roadmap and RICE prioritisation.
- Generate execution artifacts: user stories, scope specs, customer journeys, technical and design feasibility, KPIs, data privacy, go-to-market, risk registry and stakeholder roles.
- Export a styled HTML/CSS pitch presentation written to the local filesystem.
- Drive the same workflow from a local Cockpit web UI with routing and deep links.
- When to use it
- Useful when you want an assistant to structure early product discovery and specification work — market research, personas, financials, roadmaps and engineering-ready specs — from a single idea, and to produce a pitch deck from the results.
- Requirements
- Runs as a local process started with Node.js (v20+), configured in the client with the node command and the absolute path to the server script. The README states no API keys are needed. Optional Cockpit UI runs a local HTTP server, and a custom local domain requires editing the hosts file.
Installation
In SourceWeft
- Open Autopm in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
AutoPM 🚀
AutoPM is an agentic MCP server that transforms raw business ideas into complete product strategies. It orchestrates a specialized AI team to handle real-time market research, competitive deep-dives, persona building, and dynamic financial modeling, culminating in a fully-styled, pitch-ready presentation.
🟢 New to this? Check out the Quick Start Guide for Beginners for step-by-step setup instructions!
The Two-Phased Agentic Approach
Real-world Product Management requires distinguishing between finding the right thing to build and defining how to build it right. AutoPM mirrors this exact discipline through a strictly gated, two-phased workflow:
- Phase 1: Strategic Discovery ensures you are solving a real problem in a viable market before writing a single requirement. This phase answers the "Why?" and "Who?" through competitive intelligence, financial modeling, and roadmap prioritization.
- Phase 2: Execution Definition takes the validated strategy and translates it into rigorous engineering and design constraints. It answers the "What?" and "How?" by generating technical specifications, user stories, risk matrices, and success metrics.
By enforcing Phase 1 as a prerequisite for Phase 2, AutoPM prevents the most common PM trap: rushing into solution design and feature-building without a validated market strategy.
Features
- The Robot Pipeline:
- Phase 1: Strategic Discovery
- Interview Robot 🎤 - Dynamic, interactive context-gathering interview to lock in the product idea.
- Scout Robot 🔭 - Market demand analysis (TAM/SAM/SOM, growth signals, demand validation)
- Detective Robot 🔎 - Competitive intelligence (competitors, gaps, moat, positioning)
- People Robot 👥 - User personas (segments, pain points, motivations, buying triggers)
- Money Robot 💰 - Financial projections (unit economics, revenue models, 3-scenario forecast)
- Feature Robot 📝 - Feature breakdown (must-have, nice-to-have, future, with WHY/WHEN)
- Plan Robot 🗺️ - Product roadmap (phased 18-month plan with milestones, dependencies)
- Priority Robot ⭐ - Feature prioritisation (RICE scoring with principled reasoning)
- Phase 2: Execution Definition
- User Stories Robot 📖 - Epic and user story generation with acceptance criteria.
- Scope Spec Robot 🎯 - Strict scope definition, out-of-scope boundaries, and requirements.
- Customer Journeys Robot 🛤️ - End-to-end journey mapping across touchpoints.
- Feasibility Tech Robot ⚙️ - Technical architecture evaluation and constraints.
- Feasibility Design Robot 🎨 - UX/UI constraints, guidelines, and design complexity.
- KPIs Robot 📈 - Success metrics, instrumentation strategies, and target baselines.
- Data Privacy Robot 🛡️ - Security, compliance (GDPR/CCPA), and privacy risks.
- GTM Readiness Robot 🚀 - Go-to-market strategy, launch phases, and marketing channels.
- Risks Registry Robot ⚠️ - Comprehensive risk matrix and mitigation strategies.
- DACI Stakeholders Robot 🤝 - Stakeholder alignment (Driver, Approver, Contributor, Informed).
- Phase 1: Strategic Discovery
- Agentic Presentation Generator: A specialized workflow instructing Claude to act as an expert UI designer to draft and deploy beautiful, custom HTML/CSS pitch-deck presentations directly to your filesystem.
- Claude Desktop MCP Integration: Use the agents right out of the Claude MacOS/Windows desktop app.
How to Run
Via Claude Desktop (MCP integration)
- Open your Claude Desktop settings config file (
claude_desktop_config.json). - Point a new server at the Absolute Path of this project with
command: "node"andargs: ["/absolute/path/to/AutoPM/src/mcp-server.js"]. - Start the workflow using the
interviewtool, iterate viarun-robot, and export usinggenerate-presentation!
Via Other MCP Clients (Cursor, Roo Code, ChatGPT, etc.)
Because AutoPM is built on the standard Model Context Protocol (MCP), you can use it with any compatible client!
- ChatGPT macOS Desktop App: Open or create
~/Library/Application Support/OpenAI/ChatGPT/mcp.jsonand add theproductflowserver configuration similar to Claude Desktop (command:node, args:["/absolute/path/to/AutoPM/src/mcp-server.js"]). Restart the app. - Cursor: Go to Settings -> Features -> MCP. Add a new MCP server. Type:
command, Command:node, Args:/absolute/path/to/AutoPM/src/mcp-server.js. - Roo Code (VS Code): Open MCP Settings and add a configuration similar to Claude Desktop:
Via standard CLI
- Ensure Node.js (v20+) is installed
npm install- Update
run.jsto change your target product idea - Run:
node run.js
Key Folders
src/- Core MCP Server implementation (mcp-server.js)robots/- The specialized autonomous agent logicbrain/- Persistent memory, agent instructions, and user feedback engineleader/- TeamLeader orchestrator managing the flowutils/- Output engines and file toolingplans/- Auto-generated HTML presentation deliverables
Cockpit UI: Navigation & Custom Local Domain Setup
The ProductFlow Cockpit UI supports full URL routing, browser history (Back/Forward navigation), page-refresh persistence, and deep-linking via a hash-based routing system.
Custom Local Domain (autopm.ai)
Instead of accessing the Cockpit UI via http://localhost:4321, you can configure your machine to access it via a custom local domain: http://autopm.ai.
Step 1: Map the domain locally on macOS
- Open a terminal.
- Edit your system's hosts file:
- Add the following entry at the bottom of the file:
- Save and exit (
Ctrl + O,Enter, thenCtrl + X).
Step 2: Start the server
You have two options for starting the HTTP Cockpit server:
-
Option A: Run on Port 4321 (Default) Start the server normally:
Access it in the browser at: http://autopm.ai:4321
-
Option B: Run on Port 80 (No port number in URL) Port 80 is a privileged port, so you must start Node with
sudopermissions:Access it in the browser directly at: http://autopm.ai
Source: README.md at commit ff4cdb3
Tools
0Version history
1- v4.0.1LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.