create_planLABSCO SUMMARY
Dependencies stop being something you hold in your head.
The method is the ordinary one - start at the outcome and work backwards - but the payoff is the queries: what can I start now, what is blocked, and which steps actually determine the end date. Those are the three questions a plan written in a document cannot answer.
What it is
A backcasting planner. A plan starts from a desired future state and is broken into steps with dependencies; the tools then answer what can be done now, what is blocked, and which steps sit on the critical path.
What you get
- Plans created, listed, loaded and exported
- Steps added, updated, deleted and listed, with a status tracked on each
- A plan overview, and the full detail of any single step
- The next actions available right now
- The steps currently blocked
- The critical path through the plan
- An analysis pass across the whole plan
Requirements
Python. It runs locally and keeps the plans it creates - no account and no API key.
Setup effort
Build from source
USE CASES
01
Turning a goal into a sequence you can start on
Define the end state, add the steps it depends on, and read the plan back as an ordered roadmap rather than a wish.
02
Deciding what to do next
Ask for the actions that are actually available today, and mark them done as they close so the list stays honest.
03
Finding what is holding the project up
List the blocked steps and open the ones that matter, to see exactly which predecessor is the hold-up.
04
Working out which steps set the end date
Read the critical path, then run the analysis pass to see where the schedule is fragile.
05
Keeping several plans going at once
List what exists, load the one you are working on, and export it when someone else needs to read it.
14 tools
Listed in project docs. Your client may show a different list.
load_planget_plan_overviewlist_plansadd_stepupdate_step_statusdelete_stepget_step_detailslist_all_stepsget_next_actionsget_critical_pathget_blocked_stepsanalyze_planexport_planBEFORE YOU INSTALL
What to know first
Tools you get
14 tools named in the project's documentation.
Requires
Python 3.7 or later
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
TERMINAL
git clone https://github.com/NET-OF-BEING/backcast-mcp-serverMCP Clients
Claude Desktop, Claude Code
JSON
{
"mcpServers": {
"outcome-backcasting": {
"command": "python3",
"args": [
"<YOUR_PATH_TO_BACKCAST_MCP_SERVER>/mcp_server.py"
],
"env": {
"PYTHONPATH": "<YOUR_PATH_TO_BACKCAST_MCP_SERVER>"
}
}
}
}
