
Autopm
io.github.fluidumber由 GitHub 帳號 fluidumber 發布v4.0.1更新於 Oct 24, 2026
18 AI product-management robots for market research, financials, and execution specs. No API keys
概覽
AutoPM 是一個本機 MCP 伺服器,透過一組 AI 產品管理代理把商業構想轉化為經過驗證的產品策略與簡報投影片。
- 可以做什麼
- 執行嚴格分兩階段的產品流程:先做策略探索,再做執行定義。
- 透過訪談鎖定產品構想,並逐一執行市場調查、競品情報、人物誌、財務預測、功能拆解、路線圖與 RICE 優先排序等機器人。
- 產出執行類文件:使用者故事、範圍規格、客戶旅程、技術與設計可行性、KPI、資料隱私、上市策略、風險清單與利害關係人角色。
- 匯出帶樣式的 HTML/CSS 簡報投影片並寫入本機檔案系統。
- 可透過本機 Cockpit 網頁介面驅動同一流程,支援路由與深層連結。
- 適用情境
- 適合希望讓助理系統化完成早期產品探索與規格工作的情境,例如市場調查、人物誌、財務試算、路線圖與可直接交付研發的規格,並據此產出簡報投影片。
- 執行需求
- 以本機程序方式執行,需要 Node.js(v20 以上),在用戶端以 node 指令與伺服器腳本的絕對路徑設定。README 表示不需 API 金鑰。選用的 Cockpit 介面會啟動本機 HTTP 服務,使用自訂本機網域還需修改 hosts 檔案。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Autopm,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
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
來源:README.md,提交 ff4cdb3
工具
0版本歷史
1- v4.0.1最新Sep 16, 2026
評分
已滿足適用檢查項的 40%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分
請在儲存庫或註冊中心條目中宣告授權條款。