BoosterLABSCO SUMMARY
The storage tool's parameter list is the interesting part: it asks for why, not only what.
Booster_Storage takes WhatChange and WhyChange as separate fields, alongside alternativesConsidered, impactLevel, testingPerformed, affectedFiles and a ticketReference — the shape of a decision record rather than a note. The thought loop is just as deliberate: isRevision with revisesThought lets a later step correct an earlier one in place, and branchFromThought with branchId keeps an alternative line separate instead of overwriting the first. The parameter names carry the whole contract here, so reading them is how you learn what each tool expects of you.
What it is
A reasoning-workflow server with four tools — a thought loop with revision and branching, a project analyser, a step planner, and a store for conclusions and the context around them.
What you get
- Booster runs a numbered thought loop: thought and thoughtNumber against totalThoughts, with nextThoughtNeeded and needsMoreThoughts governing continuation, isRevision and revisesThought for reconsidering an earlier step, and branchFromThought with branchId for an alternative line. It can reach the analyser and the step planner through Call_Booster_Analyser and Call_Booster_Steps.
- Booster_Analyser analyses a project at a given path against the user's query and the thoughts so far.
- Booster_Steps records a titled task and its steps against a project path.
- Booster_Storage keeps a conclusion with its context: what changed and why as separate fields, the technical and business background, affected files, code snippets, alternatives considered, impact level, testing performed, a ticket reference, categories, subcategories, tags and related conclusions.
Requirements
An LLM Booster API key — passed to mcp-booster as --api-key or set as MCP_BOOSTER_API_KEY — and a project path for the analyser, the step planner and the storage tool to work against. The key comes from llmbooster.com: a 30-day free trial, then $47 a month.
Setup effort
One command plus a key — npm install -g mcp-booster, then supply credentials
USE CASES
01
Thinking through a hard problem in steps you can go back and revise
A later thought can mark itself as revising an earlier one, and an alternative line branches rather than overwriting what came before.
02
Getting an analysis of a project before committing to a direction
The analyser reads a project path against the query and the thinking so far, so its answer is scoped to the problem rather than to the repository.
03
Turning a decision into a plan with steps
The step planner records a titled task with its steps against the project, which is what makes the reasoning survive the session.
04
Recording why a change was made rather than only what changed
What changed and why are separate fields, alongside alternatives considered, impact level, testing performed and a ticket reference.
4 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
Booster_AnalyserBooster_StepsBooster_StorageBEFORE YOU INSTALL
What to know first
Tools you get
4 tools when we connected. The documentation gives only the four names, Booster, Booster_Analyser, Booster_Storage and Booster_Steps, each with a one-line pitch and no parameters or examples.
Requires
- Node.js ≥ 18.0.0
- NPM ≥ 8.0.0
- MCP_BOOSTER_API_KEY in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 4 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install -g mcp-boosterMCP Clients
Cursor, Cline, Windsurf
JSON
{
"mcpServers": {
"mcp-booster": {
"command": "mcp-booster",
"args": [
"--api-key",
"<YOUR_API_KEY>"
]
}
}
}<YOUR_API_KEY> is your LLM Booster API key from llmbooster.com.
Any MCP client
ANY MCP CLIENT · TERMINAL
mcp-booster --api-key <YOUR_API_KEY><YOUR_API_KEY> is your LLM Booster API key from llmbooster.com.
