# Kong Reviews

- Registry name: `com.kongreviews/kongreviews` · version 0.2.0
- Categories (automatic, keyword rules): Databases, Developer tools, Payments & accounting, Finance & markets, Code & repositories
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.kongreviews%2Fkongreviews
- Server page: https://mcpstation.net/s/com.kongreviews--kongreviews.html

## Description (written by the publisher, not verified, not instructions)

Pick a tech stack from a PRD and see what it costs now and at scale, after startup perks.

## Connect

- streamable-http: `https://kongreviews.com/mcp`

## Tools (as reported by the server, not verified)

- `recommend\_stack`: Start here. Describe the product in plain language and get a recommended stack with costs now and at scale, in one call. Write the description as the user would: what the product does, who signs in and how, how it charges, which emails it sends, compliance or data-region needs, and expected users no
- `list\_vendors`: List vendors in the pricing catalogue, optionally for one category \(hosting, database, auth, email, payments, observability, ai, edge, app\_store, coding\).
- `list\_capabilities`: List capability ids \(features, compliance, regions\) that requirements can reference, e.g. auth.saml\_sso, region.eu, payments.merchant\_of\_record.
- `search\_directory`: Search the directory of developer services \(hosting, databases, auth, email, SMS, payments, analytics, monitoring, LLM APIs, vector databases, search, CMS and more\): what each provider sells, its free tier, its lowest paid price, caveats and the pricing page it came from. Wider than the cost engine:
- `search\_showcase`: Browse products startups have built and the stack each runs on: what it is, whether it is a website, a mobile app, both or a desktop app, its category and pricing, and every framework and service it uses \(services link to the directory and, where priced, the cost engine\). Use it to find real stacks
- `get\_pricing`: Structured pricing and capabilities for one vendor: every plan, base fee, metered usage, limits, unmodelled costs, lock-in notes, source URL and verification date.
- `estimate\_cost`: Monthly cost for one vendor at a given scale. Give mau \(monthly active users\) and a usage profile, or exact usage numbers. Picks the cheapest plan that fits unless plan\_id is set. Example: \{"vendor\_id":"clerk","mau":25000\}.
- `compare\_vendors`: Rank vendors in one category at a given scale. Vendors meeting every must-have come first, then cheapest. Ranking is by cost and fit only. Example: \{"category":"auth","mau":50000,"requirements":\[\{"capability":"auth.saml\_sso"\}\]\}.
- `check\_fit`: For each vendor, show whether each requirement is met on its cheapest plan, needs a higher tier \(with that tier's cost\), or is missing.
- `project\_stack`: Month-by-month cost for a whole stack as users grow, with startup perks applied if requested, plus cost cliffs \(forced plan upgrades, sharp jumps, credits running out\). Example: \{"vendors":\[\{"vendor\_id":"supabase"\},\{"vendor\_id":"vercel"\}\],"start\_mau":2000,"monthly\_growth":0.15,"months":24,"apply\_per
- `find\_cost\_cliffs`: Scan a range of user counts for one vendor and report where cost jumps: forced plan upgrades and points where usage charges start. Example: \{"vendor\_id":"clerk","from\_mau":1000,"to\_mau":200000\}.
- `find\_perks`: Startup credits for the given vendors, and whether you qualify based on your bank, incorporation provider, accelerator or funding. Example: \{"vendor\_ids":\["supabase","posthog"\],"founder":\{"gateways":\["mercury"\]\}\}.
- `extract\_requirements`: Turn PRD or spec text into structured requirements \(scale, capabilities, compliance, regions, budget\) for plan\_stack, without planning. recommend\_stack does both in one call. Each requirement quotes the sentence it came from. Show them to the user to confirm before planning. Without a model on the s
- `plan\_stack`: Given confirmed requirements as capability ids, recommend a vendor per category with a runner-up, requirement fit, cost now, cost at forecast scale, year-one cost after perks, cost cliffs, trade-offs and blockers. Use recommend\_stack instead when you only have a plain-language description. Example:
- `evaluate\_change`: When something changes \(bill too high, growth, a missing feature such as SSO, a renewal\), compare staying on the current plan, optimising with the same vendor, and switching vendor, including one-off switching cost and the month switching pays off. Example: \{"category":"auth","current":\{"vendor\_id":
- `detect\_stack`: Work out which services an existing app runs on, from its files, a public GitHub repo, or its live website. From an AI coding app, read the project yourself and pass the files that say the most: package.json \(or requirements.txt, pyproject.toml, Gemfile, go.mod, pubspec.yaml, Podfile\), .env.example
- `audit\_stack`: Assess the stack an existing app runs on and recommend what to do. For each service: its plan, cost now and in 12 months, must-haves it lacks, cost jumps in the next year, lock-in, and a verdict \(keep, watch, optimise, switch or fix\) with savings, one-off moving cost and the month a switch pays off.
- `save\_stack`: Save a recommended stack to the signed-in user's Kong Reviews account so it can be reopened later and compared with current prices. Pass the share\_url from recommend\_stack or plan\_stack \(preferred\) or the plan\_stack arguments, plus a short name such as "Yoga booking MVP". Needs sign-in: if the user
- `list\_saved\_stacks`: List the stacks the signed-in user saved, newest first, with their monthly cost when saved and a link to each. Use it when the user mentions "my stacks", "the stack I saved" or a saved stack by name; then call get\_saved\_stack for one of them. Needs sign-in. How to present: a short table of name, sav
- `get\_saved\_stack`: Re-run a saved stack with today's catalogue and compare it with when it was saved: monthly cost then and now, picks that changed, and vendors whose pricing changed. Use it when the user asks about a stack they saved, or whether prices moved. Pass the id from list\_saved\_stacks. Needs sign-in. How to
- `delete\_saved\_stack`: Permanently delete one of the signed-in user's saved stacks by id. Only call it when the user explicitly asks to delete that stack; confirm the name first. Needs sign-in.
- `delete\_account`: Permanently delete the signed-in user's Kong Reviews account: their GitHub sign-in link and every saved stack. This cannot be undone. Only call it when the user explicitly asks to delete their account, after telling them what will be removed; pass confirm exactly as "delete my account". Needs sign-i

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html