
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 分
请在仓库或注册中心条目中声明许可证。