start_project_planningLABSCO SUMMARY
It interviews you first.
Most stack advice fails because it answers a question you have not framed yet; this one uses elicitation to build the requirements before it recommends anything, and stays on managed platforms so the recommendation ends in a deployment rather than an architecture debate. Recommendations come from rules over your answers, so treat the explanation as the useful part.
What it is
A tech-stack planning MCP server. Rather than returning a framework comparison, it asks about the project — what you are building, who uses it, how many of them, budget, and how technical you are — and turns the answers into a concrete stack with deployment steps.
What you get
- An interactive planning session that gathers requirements through MCP's elicitation spec, in plain language —
start_project_planning - A stack recommendation built from those requirements, usable with or without the interview —
recommend_stack - The reasoning behind the picks at a
basicordetailedlevel —explain_recommendation - Step-by-step deployment instructions for the platform you land on —
get_deployment_guide - A bias toward managed platforms — Vercel, Netlify, Supabase, PlanetScale, Firebase, Render — so the answer is something a small team can actually run
Requirements
Python with uv pip install fastmcp, then python run_server.py. The documented client entry points at run_server.py by absolute path, so the checkout lives on the machine running the client. The project is vibe-coder-stack-planner 0.1.0.
Setup effort
Clone and run — clone the repository, then add the configuration for your client; uv runs the script from your clone, with nothing to build
USE CASES
01
Starting a project without a stack in mind
Answer a short series of plain questions and get a concrete frontend, backend, database and hosting choice.
02
Sanity-checking a stack you already chose
Skip the interview, pass what you have in mind, and read back why each piece was or was not recommended.
03
Getting from decision to deployment
Ask for the deployment guide for the platform you picked instead of assembling it from three docs sites.
04
Explaining the choice to a non-technical partner
Ask for the basic explanation level and hand over the reasoning without the jargon.
4 tools
Listed in project docs. Your client may show a different list.
recommend_stackexplain_recommendationget_deployment_guideBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Clone the repository, then add the configuration for your client; uv runs the script from your clone, with nothing to build.
Server setup
TERMINAL
git clone https://github.com/memextech/vibe-plan-mcp.gitMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"vibe-stack-planner": {
"command": "uv",
"args": [
"run",
"--directory",
"<YOUR_PATH_TO_VIBE_PLAN_MCP>",
"python",
"run_server.py"
]
}
}
}
