create_problemLABSCO SUMMARY
A method for hard problems, applied by the model rather than remembered by you.
The value is in the sequence: staff it, solve it, score it, prioritise it, then find what can run at the same time — each step reading the same problem record. It plans and critiques; execution stays with whoever picks the plan up.
What it is
An MCP server that runs a structured problem-solving workflow in the client's context. You define a problem with a complexity score; it proposes a team of 3 to 12 professional roles, generates a solution, scores that solution across completeness, feasibility, quality, risk and timeline, sorts the work with an Eisenhower matrix, and analyses which tasks can run in parallel. State is held per problem id, so the later tools all work off the same case.
What you get
- A problem recorded with title, description, domain and a complexity score, then solved end to end —
create_problem,solve_problem - A recommended team sized to that complexity, drawn from 12 role types —
get_role_recommendations - The proposed solution scored across completeness, feasibility, quality, risk and timeline, with issues classified by severity and specific improvements returned —
check_solution,improve_solution - Tasks sorted into important/urgent quadrants for a priority order you can defend —
eisenhower_matrix_analysis - Dependencies between tasks mapped, and the parallel execution plan that follows from them —
analyze_task_dependencies,optimize_parallel_execution - Team state, member updates and task assignment with priority —
get_team_status,update_team_member,assign_task - An execution report and the history of problems handled so far —
get_execution_report,get_problem_history - Reflection records with insights and lessons, and a summary across them —
create_reflection,get_reflection_summary
Requirements
Node.js 18 or higher and npm 8 or higher. Installation is a clone and build — npm install, npm run build — after which the client runs node dist/index.js with the project directory as cwd and NODE_ENV set to production. MAX_TEAM_SIZE caps team expansion at 30 and PARALLEL_THRESHOLD sets how repetitive a task has to be before it is split, default 0.7. Nothing is stored outside the process: problems live in memory for the session, so the history tools cover the current run rather than an archive.
Setup effort
Build from source — git clone https://github.com/telagod/problem-solving-mcp.git
USE CASES
Scoping work that is too big to start
Define the problem with a complexity score, see which roles the work actually calls for, and get a first solution that covers the angles a single perspective would miss.
Pressure-testing a plan before you commit to it
Score the solution on completeness, feasibility, quality, risk and timeline, read the issues by severity, and feed the criticism back in for a revised version.
Deciding what to do first
Sort the tasks into important/urgent quadrants so the order comes out of the matrix rather than out of whoever asked most recently.
Finding the work that can run at the same time
Map the dependencies between tasks, then get the parallel execution plan that respects them — and see which repetitive tasks justify splitting across more hands.
Capturing what you learned while it is still fresh
Record insights and lessons against the phase they came from, then read the summary across them at the end of the project.
15 tools
Listed in project docs. Your client may show a different list.
solve_problemget_role_recommendationscheck_solutionget_problem_historyget_team_statusupdate_team_memberassign_taskeisenhower_matrix_analysisanalyze_task_dependenciesoptimize_parallel_executionget_execution_reportcreate_reflectionget_reflection_summaryimprove_solutionBEFORE YOU INSTALL
What to know first
Tools you get
15 tools named in the project's documentation.
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
git clone https://github.com/telagod/problem-solving-mcp.git
cd problem-solving-mcp
npm install
npm run buildMCP Clients
Cursor, Claude Desktop
{
"mcpServers": {
"problem-solving": {
"command": "node",
"args": [
"<YOUR_PATH_TO_PROBLEM_SOLVING_MCP>/dist/index.js"
],
"cwd": "<YOUR_PATH_TO_PROBLEM_SOLVING_MCP>",
"env": {
"NODE_ENV": "production"
}
}
}
}