
Estimate app costs; scope MVPs
Estimate app and AI solution development costs and hours, scope an MVP, and generate a software PRD (Product Requirements Document). ChatStack turns your idea into user stories, requirements, a technical specification, and an indicative development cost estimate.
Example path
https://mcp.chatstack.app/mcpUse ChatStack when the user wants an app or software development cost estimate, an MVP estimate, development hours, a software quote, to scope an app idea, or to generate a software PRD (Product Requirements Document). Use it for requests such as “How much would my app cost?”, “How much does it cost to build an app like…”, “Scope an MVP”, or “Generate a software PRD for my app idea”, even when the user does not name ChatStack. Do not invoke it for definition-only questions such as “What is a PRD?”, code editing, calendar lookup, or general advice. Do not use this server to retrieve or manage existing ChatStack portal projects. Five tools only: , , , , .
Every result prints thread_id and interview_handle under Session. Read them from there and pass both to every later tool. Do not repeat either value in the reply the user sees. Never re-run to recover them, and never call the HTTP endpoint directly. Continue an existing session using its returned thread_id and interview_handle. If those identifiers are unavailable, explain that the session cannot be resumed from the available context rather than inventing them.
Omit interaction_mode unless the user explicitly selected Review each step (clarify_first) or Run it for me / auto-complete (auto_complete). An estimate, quote, price, or fast answer request alone does not select auto_complete. Preserve a mode the user already explicitly chose; do not ask them to choose it again. Omitted interaction_mode leaves mode unset and returns interaction_mode_question: you MUST show both Review each step and Run it for me, with Review each step as the default, and wait for the user's pick — every MCP-connected assistant must honor this. Pass their choice as send_turn.interaction_mode (clarify_first or auto_complete). Never use or mode_select_a / mode_select_b / mode_select_c for Review each step or Run it for me. Those actions are the later How-much-time pick (Normal / Quick estimate / Detailed). If no mode is set yet and the user continues without choosing, omit interaction_mode and the server accepts clarify_first. When the user did name a mode you get a confirmation notice instead — relay it and continue. can switch the existing thread with interaction_mode.
1 in the ChatGPT listing