ChatStack - App Cost Estimator
v1.0.0Estimate development costs and hours, scope an MVP, and write a PRD with user stories and specs.
Endpoint health
online- Last checked
- 11/20/2026, 5:17:03 AM
- Latency
- 120 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:app.chatstack%2Fapp-cost-estimator
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"app.chatstack/app-cost-estimator": {
"url": "https://mcp.chatstack.app/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
5 shown · authentication unknown
Get app estimate progress
get_estimate_status
Read 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 interview_handle from the Session section. Do not call start_session to recover a session, and do not use this tool to approve, edit, or submit.
Schema valid · SHA-256 853ec169f9cf…
View input schema
{ "type": "object", "properties": { "thread_id": { "type": "string", "minLength": 1, "description": "Interview thread id from start_session." }, "interview_handle": { "type": "string", "minLength": 1, "description": "Opaque interview handle from start_session. Pass it on every later tool." } }, "required": [ "thread_id", "interview_handle" ], "$schema": "https://json-schema.org/draft/2020-12/schema" }Submit the pending choice
send_action
Submit 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 not ask the user to choose – show the user that milestone's Auto-complete decision receipt and pipe-table. Do not ask them to approve it. Call send_action once per result, and only again on the next result while next_tool is send_action. When next_tool is submit_prd, stop and offer submission. An approve moves one phase: stories to requirements, requirements to the technical spec, then the tech spec to the estimate. In Review each step, stories_reject, requirements_reject, and techspec_reject show the current table again and wait. When the user describes the change, call send_turn with their exact words and show the regenerated table that comes back. mode_select_a, mode_select_b, and mode_select_c are only the How much time pick: Normal, Quick estimate, or Detailed. Do not use them for Review each step or Run it for me. That choice is send_turn with interaction_mode. For clarifying_questions_submit, set payload.answers by question id with the letter only, such as {"q1":"A","q2":"B"}, not "1A". A plain reply such as "1B, 2A, 3C", or any wording that combines options, goes through send_turn. Do not split one question into several letters.
Connections
streamable-http
https://mcp.chatstack.app/mcp