ChatStack - App Cost Estimator

app.chatstack/app-cost-estimator · v1.0.0 · communication

ChatStack - App Cost Estimator is healthy: it completed an MCP handshake in 1005 ms and exposes 5 tools.

Estimate development costs and hours, scope an MVP, and write a PRD with user stories and specs.

Endpoint: https://mcp.chatstack.app/mcp (streamable-http)

No repository listed · Website · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count5
Latency1005 ms
Last checked (UTC)2026-10-29T12:55:22.884Z

Health history

Checked (UTC)StatusLatencyError
2026-10-29T12:55:22.884ZHealthy1005

Tools (5)

start_sessionStart a guided session to estimate app development cost, scope an MVP, and generate a software PRD. No portal account or personal access token is required. Call it with no arguments unless the user already named Review each step (clarify_first) or Run it for me (auto_complete). Do not choose an inte
send_turnContinue an app cost estimate by sending the user's answers or requested changes to the MVP scope, user stories, requirements, or technical specification. Pass their exact words in input_as_text, even when next_tool is send_action. Compact replies such as "1A, 2B" are valid. Preserve the user's sele
send_actionSubmit the user's pending choice. Set action_type to a value from pending_gate_payload.allowed_actions. In Review each step, action_type is required; confirmed_by_user=true is preferred and is not a substitute for it. In Run it for me, omit action_type and payload to advance one milestone, and do no
get_estimate_statusRead the current app cost estimate without advancing it. Returns flow_stage, pending_gate, and pending_gate_payload. After submission it also returns post_submit_notice and post_submit_links: relay the notice verbatim, keep every URL, and do not add an email-delivery caveat. Pass the thread_id and i
submit_prdSubmit the completed software PRD and app development estimate for email delivery and portal project creation. Call it only after user stories, requirements, tech specs, and the estimate exist. (flow_stage estimate). Run it for me stops at this tool. Offer submission and wait for the user. Do not su