ai-product-planner
Provides integration with NVIDIA's OpenAI-compatible endpoint (e.g., z-ai/glm-5.2) for generating product planning outputs, supporting structured JSON output.
Integrates with any OpenAI-compatible Chat Completions API to generate structured product planning packages including PRDs, requirements, user flows, wireframes, data schemas, API contracts, and MCP handoff resources.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ai-product-plannerplan a habit tracker app with streaks and reminders"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
AI Product Planner
AI Product Planner turns a product idea into an implementation-ready planning package: PRD, requirements, user flow, wireframes, data schema, API contracts, SDK boundaries, and an MCP handoff for coding agents.
The generation pipeline uses a supervisor stage followed by dependency-aware parallel workers. It calls any OpenAI-compatible Chat Completions API and keeps generated sessions on the local filesystem.
Requirements
Node.js 22 or newer
An OpenAI-compatible LLM API key and model with structured JSON output support
Related MCP server: DinCoder
Quick Start
npm install
cp .env.example .env
# Set PLANNER_LLM_API_KEY and, if needed, the base URL and model.
npm run build
npm startOpen http://127.0.0.1:8792.
For frontend and backend development in separate terminals:
npm run dev:server
npm run devLLM Providers
The default example targets NVIDIA's OpenAI-compatible endpoint with z-ai/glm-5.2. Other providers work when they implement POST /chat/completions with messages, response_format, and choices[0].message.content.
Set PLANNER_LLM_STRUCTURED_OUTPUT=false only when the selected provider does not support response_format: { "type": "json_object" }. The planner still validates the returned JSON and fails explicitly if the contract is invalid.
Authentication
The default server binds only to 127.0.0.1 and allows unauthenticated local use. It refuses to start with PLANNER_AUTH_MODE=none on a non-loopback host.
For deployment behind an access proxy, use header mode:
HOST=0.0.0.0
PLANNER_AUTH_MODE=header
PLANNER_AUTH_HEADER=x-authenticated-user
PLANNER_AUTH_HEADER_VALUE=expected-proxy-valueYour proxy must strip incoming copies of that header and inject the trusted value after authentication. MCP clients can instead use PLANNER_MCP_BEARER_TOKEN.
MCP
The JSON-RPC MCP endpoint is /mcp. It exposes planning sessions, generated contracts, active implementation goals, and run handoff resources.
curl http://127.0.0.1:8792/mcp \
-H 'content-type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'Commands
npm test
npm run lint
npm run typecheck
npm run buildSee SERVER_START_HERE.md, SERVER_OPERATIONS.md, and APP_DATA_SCHEMA.md for integration details.
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/codenameju/ai-product-planner'
If you have feedback or need assistance with the MCP directory API, please join our Discord server