SatisfactoryMCP
SatisfactoryMCP is a local MCP server that reads Satisfactory saves and helps Claude analyze factories, plan production, rank upgrades, and show results on a map.
Read worlds/saves: list worlds, summarize progress/power/problems, inspect phases, research, inventory, crates, boosters, and collectibles.
Analyze factories: name/propose/select factories, view floors, query recipes/buildings/power/links/issues, diagnose stopped machines, trace feeds, and inspect belts/pipes.
Diagnose health: find blocked/starved/stalled/paused machines, missing power, fluid/head-lift/plumbing faults, and full-storage vs real blockages.
Plan production: solve LP/MILP plans over unlocked recipes for target rates or power, with machines, clocks, raw inputs, byproducts, exports, power, layout, commissioning waves, and save diffs.
Optimize choices: bill of materials, recipe-route comparisons, byproduct explanations, hard-drive/unlock ranking, and build-site ranking.
Query game data: search items/recipes/buildings, recipe details, alternates, unlocked recipes, resource nodes, regions, and locations.
Work spatially: show map links, describe coordinates/regions/terrain, find nearby conduits/resources/sites, and pin locations.
Manage project state: edit factory names/storage stance, save/version/share/import plans, record plan sitings, and change shared settings/UI context.
Stay save-safe: game saves are only read; edits affect SatisfactoryMCP metadata (factory labels, plans, settings, pins), not the save file.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@SatisfactoryMCP plan a factory for 10 turbo motors per minute using my save"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SatisfactoryMCP
Ask Claude about a Satisfactory factory. SatisfactoryMCP is an MCP server that reads the save files on this PC and answers in chat: what runs, what stands still and why, what to build next and how, planned with a real optimizer over the game's own recipe data and the recipes the world has unlocked. A local web page draws the same world on a map. Everything runs on the player's PC and only ever reads saves.
An unofficial fan tool for Satisfactory. Not affiliated with or endorsed by Coffee Stain Studios. Satisfactory and game assets © Coffee Stain Studios AB.
Ask Claude about the factory
Phrased however the player likes; Claude picks the tools. Four questions and what comes back:
How healthy is the steel factory? Anything blocked or starved?
factory_health lists the machines that need action, grouped by state and cause, and tells a
line backed up into full storage (stock done) from a real blockage: a torn belt, a feed that
brings the wrong item, an output that leads nowhere.
Plan 20 Modular Frames a minute with what I have unlocked. What do I build?
plan_factory solves over the unlocked recipes and answers with the buildings per recipe at
their clocks, the raw inputs, the power drawn and the belt or pipe each flow needs, warnings
first: a whole machine for a sliver of a rate, unused Somersloops, a byproduct with no outlet.
A setup that would strand a byproduct is reported infeasible, not overstated. The plan's handle
goes on to plan_layout, commission_plan and diff_vs_save.
Which hard drive should I open first?
hard_drives ranks the unclaimed drives by what each alternate would save against the goals
and saved plans: machines and power off the bill, and need against supply.
Show the coal power plant on the map.
show_on_map answers with a link into the local map, centred on it.
Every answer names the save it read and how old it is. All 49 tools, the prompts and the resources: docs/mcp-surface.md.
Related MCP server: minecraft-diagnostic-mcp
Quick start
Needs Python ≥ 3.11 with uv, and a local Satisfactory install (Steam or Epic): recipes and rates come from the game's own data dump, so they stay right when the game patches. Node.js only builds the page. Developed and tested on Windows, where saves and the install are found on their own; elsewhere, set their paths (configuration).
Chat
git clone https://github.com/lukszi/SatisfactoryMCP.git
cd SatisfactoryMCP
uv syncRegister it in Claude Code, at user scope so it loads in any directory:
claude mcp add --scope user satisfactory -- uv run --directory "/path/to/SatisfactoryMCP" satisfactory-mcpClaude Desktop (claude_desktop_config.json) and other stdio clients:
{
"mcpServers": {
"satisfactory": {
"command": "uv",
"args": ["run", "--directory", "/path/to/SatisfactoryMCP", "satisfactory-mcp"]
}
}
}Then open a new chat and ask. satisfactory-mcp finds the local server or starts one, so every
chat and the page share one process, which ends itself after 10 minutes unused. Its commands
(stop, start, restart, status): docs/hosted-seams.md.
Updating: docs/releasing.md; from 0.2:
docs/upgrading-to-0.3.md.
The page
Build the page once, or unzip a release's static.zip into
packages/satisfactory-web/src/satisfactory_web/static/; then cut the item and building icons
from the installed game (again after a game update):
cd packages/satisfactory-web/src/satisfactory_web/frontend
npm ci && npm run build
cd -
uv run --extra gen python tools/gen_item_icons.pyThe page is at http://127.0.0.1:8712, served by the same process: the first chat starts it,
or uv run satisfactory-mcp-web. It binds to localhost on purpose, because the API answers with
the contents of the save folder and has no authentication. Base maps are made on its map studio
(#maps), which names any setup still missing.
A page served elsewhere: the helper
The page also builds to run in the browser with no server
(docs/hosted-seams.md). Served from a site or from this
PC, it reaches the saves through sf-companion, the helper on the player's PC, which also
serves the tools to a chat:
uv run --package sf-companion sf-companion serve --server https://<site>
claude mcp add --scope user sf-companion -- uv run --directory "/path/to/SatisfactoryMCP" --package sf-companion sf-companion mcp --server https://<site>For a page served from this PC, pass --origin http://127.0.0.1:<port> instead of --server.
sf-companion import-local brings the local app's factory names and plans over, and
sf-companion claude-command prints the Claude Code command line that loads the game channel,
for requests typed in the game (a preview). Every command, and installing the helper from a
release without a clone: docs/companion.md.
What it can do
Read the world: power circuits in the game's terms, factories found and named from the save, machine health with causes, fluid head lift, inventory and crates, phases, research, hard drives, Power Shards and Somersloops.
Plan: an LP/MILP optimizer over the game's recipes and the world's unlocks, byproducts balanced, with layouts, commissioning against the save, unlock ranking and build sites; saved plans keep their history and share as links, text or files (docs/planning.md).
Show it: a page with the map, factories, power, progress, items, world and planner, following the saves live as the game writes them.
Answer in the game: the helper's game channel passes requests from an in-game mod to a running Claude Code session and the answer back (docs/companion.md).
The map
Factories, belts, pipes, power and resource nodes drawn over a base map: the game's own artwork, or a satellite, relief or terrain map rendered from the game's data by the map generators (tools/mapgen/README.md), lit by a live sun.

|
|
Docs and packages
Document | Covers |
the design spine and the index of every spec document | |
every tool, prompt and resource | |
the optimizer, layout and unlock ranking | |
coordinates, regions, selectors and the map | |
the one process, the shim, map links, the stores, the browser runtime | |
the helper: commands, install, the game channel | |
development setup, tests, architecture rules | |
versions, branches, updating, releases | |
what changed, with upgrade notes |
One uv workspace, nine wheels at one version; each package's README says how to use it alone:
Package | Holds |
the save parser, standard library only | |
readers for the game's asset container, for the map and data generators | |
game data, saves, the domain and planner, the JSON API as plain calls | |
the MCP tools, the stdio server, the shim | |
the web API and the page | |
| the one process, its lifecycle, the console scripts |
the helper on the player's PC | |
the helper's records file and edits API | |
a packed save projection's metadata |
Licence
PolyForm Shield 1.0.0. Free for any use except providing a product, paid or free, that competes with this software or with any product the licensor provides using it. Copies must carry the licence terms (or their URL) and the required notice:
Required Notice: Copyright Lukas Szimtenings (https://github.com/lukszi/SatisfactoryMCP)
Licensor Line of Business: Satisfactory save analysis, factory planning and map software and hosted services (https://github.com/lukszi/SatisfactoryMCP)
A competing product needs a separate licence from the licensor — get in touch via GitHub (@lukszi). The licence covers this repository's code, tooling and extracted tables; it cannot and does not grant anyone rights over the game's content, which Coffee Stain Studios retains. The page bundles Leaflet (BSD-2-Clause) at build time, with its licence text beside every build.
Contributions are accepted under the CLA; the steps are in CONTRIBUTING.md.
Available Tools
49 toolsalternates_for_itemBRead-onlyIdempotent
Every recipe that makes an item, alternates first, marked HAVE/LOCKED against the save.
A LOCKED row names the schematic that grants it. With plan: each recipe's status in
that plan and the machine, MW and raw-input deltas of requiring it.
Inputs: item (required), plan, save, as_of, +2 more.
bomBRead-onlyIdempotent
Flattened bill of materials for qty/min of an item: raw and intermediate rates, chosen recipe and machines per row.
qty is a rate per minute. Solved by LP, not tree expansion (recipe cycles have no safe depth), so each row names its recipe; alternates change the totals.
Inputs: item (required), qty, save, as_of, +7 more.
boostersARead-onlyIdempotent
Power Shards or Somersloops: free, committed and owned, and which machines hold them.
kind=shards also says whether plan_machines at plan_clock fit the free shards, or
the ones craftable from slugs in hand.
Inputs: kind, save, as_of, limit, +4 more.
collected_from_worldARead-onlyIdempotent
Map collectibles (slugs, sloops, spheres, mushrooms, drop pods): how many exist, taken, left, closest.
Existence is read from the installed game's map data, removal from the save's destroyed-actor list; remaining is the difference. show=census counts per category; collected and remaining list placements with coordinates; nearest lists remaining by distance from near=. A placement this save never loaded counts as remaining, flagged never_streamed.
Inputs: near, save, show, as_of, +4 more.
commission_planARead-onlyIdempotent
Startup order for a built plant: which blocks to energise in which wave without blowing the fuse.
Not a build order: build everything first, then energise wave by wave. A wave's consumer draw must fit in headroom plus the output of generators already burning, or the fuse blows and stops the whole grid until reset by hand. Generators energise free and pay for the next wave.
Inputs: plan (required), save, as_of, limit, +4 more.
compare_recipe_optionsARead-onlyIdempotent
Rank whole routes to make an item by cost: raw per unit, buildings, net power, byproducts needing an outlet.
Each route is solved end to end (Crude -> Alt HOR -> Diluted Fuel against Crude -> Fuel); alternates_for_item only lists recipes.
Inputs: item (required), rate, save, as_of, +5 more.
cratesBRead-onlyIdempotent
Crates on the ground (death and dismantle crates): contents and where to walk to.
Recoverable, never spendable stock.
Inputs: save, as_of, limit, world, +1 more.
describe_locationARead-onlyIdempotent
What is at a place: region, terrain height, sampled elevations, belts and pipes through it, nearest node and field.
terrain_m is the terrain field's reading at the point (water surface and depth where it stands); ground and built elevations are sampled from nodes and buildings within radius_m, never averaged, and their gap is fill already stacked. Conduit counts read the save: zero means nothing runs through; search_conduits lists them.
Inputs: at, save, as_of, world, +1 more.
diff_vs_saveARead-onlyIdempotent
Steps from the factory as built to a plan: UNPAUSE, SETRECIPE, then BUILD, with the power the new machines add.
Re-solves the plan. Machines match by identity (building + recipe; generators by building; extractors by node), never by position; one on another recipe is busy. Water Extractors cannot be identified, so their count is a range. A saved plan's diff is grouped by startup stage (commission_plan's partition): stage=n narrows to one, stage=0 shows the stage overview of an unsaved solve. Power is proven one way only: a machine that produced in its last 300 s had power; one that did not is 'nothing proven running', never 'unpowered'. Read-only, no dismantle action: machines on the plan's ground but not in it are listed for you to judge.
Inputs: plan (required), save, as_of, limit, +5 more.
edit_factoryADestructive
Name, amend, rename or forget a named factory (a set of machine ids), or set its storage stance.
Ids survive moves and autosaves. name on an existing name replaces its machines. amend adds, drops, then prune_missing clears gone anchors; one machine is machine:; the last can't be dropped. rename: saved plans follow. forget keeps the machines. storage: is full storage at a line's end stock or a blockage. dry_run previews.
Inputs: name (required), action (required), to, add, +10 more.
edit_planADestructive
Rename, forget, undo or restore a saved plan; each edit is a new version and needs base_rev. Nothing is re-solved.
rename keeps key, siting and notes; forget deletes it (undoing that version brings it back); undo writes the inverse of version=; restore makes the head equal version= again.
Inputs: name (required), action (required), to, save, +4 more.
explain_byproductsBRead-onlyIdempotent
Which byproduct stalls a plan (INFEASIBLE) and what can consume it: sink (solids only) or recipes, unlocked vs locked.
Item balances are equalities, so an unconsumed byproduct makes the solve infeasible; a fluid must be consumed or packaged first. Reads an infeasible solve: handle too.
Inputs: plan (required), item, save, as_of, +2 more.
factory_floorsARead-onlyIdempotent
Floors of a foundation platform: how many decks and what stands on each.
Floors are recovered from geometry (clustered foundation tops, no assumed pitch); a band under a quarter of the largest deck is marked minor (mezzanine or plinth). Default: one row per platform, largest first. platform= (index stable on one save) or factory= narrows to one platform, answered floor by floor.
Inputs: save, as_of, limit, world, +3 more.
factory_healthARead-onlyIdempotent
Why machines are stopped: measured uptime per machine and each stopped one's cause; 'all' sweeps.
Uptime: share of the save's 300 s productivity window spent producing. States, worst first: paused, dead node (extractor on no resource), no recipe, blocked (output full), starved (input short), stalled (input and room, still not running), intermittent, saturated, unmonitored; todo counts the first five. A machine no generator reaches over the wires says so (no wire, or a circuit with no generator); a reachable one is never called unpowered. A starved machine names its missing input's feeder one hop back (the run, its far end, that feeder's state); trace_upstream walks further. A missing fluid is diagnosed on the plumbing ladder: connection, head lift, flow rate; the first failing rung is the cause. factory='all' adds world-wide plumbing faults: fluid buffers too low to output at intake rate, unwired pipeline pumps, lines above head lift. offset pages every table at once.
Inputs: save, as_of, limit, world, +2 more.
factory_mapARead-onlyIdempotent
Raw factory signals: power islands (base:), belt components (line:), foundation slabs (slab:).
Also the named factories. Islands merge a grown-together base, belt components fragment it, slabs are sharpest but miss ground-built machines; propose_factories combines them. Where they disagree, carve with edit_factory and a product:, near: or slab: term. show=slabs also lists bare platforms (foundations with no machine) with tile count, extent and elevation.
Inputs: save, show, as_of, limit, +2 more.
factory_queryBRead-onlyIdempotent
One question about one factory: what it makes, needs, draws or touches; show= takes several views.
Every rate is nameplate (at the saved clock) and measured (scaled by each machine's 300 s productivity window, so an idle line measures 0 without being broken); unmonitored machines are shown apart. offset pages every table at once.
Inputs: factory (required), save, show, as_of, +3 more.
factory_sitesCRead-onlyIdempotent
Built production buildings clustered by distance into sites, largest first, each with a near: selector.
The selector goes in as a select= term or as factory=; propose_factories groups by more than distance.
Inputs: save, as_of, limit, world, +1 more.
hard_drivesBRead-onlyIdempotent
Unclaimed hard drives, each with its pick and why; drive=N details one drive.
Measured on this world: shortages, open goals, raw saved on what is built, grid MW.
sources= adds a build-out solve on those nodes, as plan_factory does.
Inputs: save, as_of, drive, limit, +3 more.
import_planC
Import a shared plan (link, sfplan: line or file) as a new plan.
Inputs: text (required), name, save, as_of, +1 more.
inventoryARead-onlyIdempotent
What you own: per-item totals, or each container, crate and fluid buffer with place and fill (show=containers).
spendable = carried + storage + Dimensional Depot, the pool every cost check spends;
machine buffers and crates are shown apart, never added in. Fluids are m3. item=
narrows either view; near=, container_kind= and empty= are containers-only.
Inputs: item, near, save, show, +7 more.
list_buildingsARead-onlyIdempotent
Buildings by kind: power, max clock, sloop slots, footprint; marked HAVE/LOCKED against the save.
logistics also names the fastest unlocked belt and pipe, which planning assumes. Pages
with offset=; all is hundreds of rows.
Inputs: save, as_of, limit, world, +2 more.
list_factoriesBRead-onlyIdempotent
Named factories of this world (the names factory= takes), with how much of each still stands.
Inputs: save, as_of, world.
list_regionsARead-onlyIdempotent
Named map regions with anchor coordinate, area and node count; resource= keeps regions holding it.
Names are advisory (boundaries about 256 m); any name works as a region: selector. The anchor provably lies inside the region.
Inputs: resource.
list_worldsBRead-onlyIdempotent
Saves grouped by world, newest first: the names save= and world= take (default: newest save).
world= lists one world's saves, offset= pages them.
Inputs: world, offset.
phase_requirementsCRead-onlyIdempotent
Space Elevator: the current phase and what it still wants.
The save's per-phase item table is deprecated; trust the header line over it.
Inputs: save, as_of, world.
plan_factoryA
Solve a factory plan by LP over this world's unlocked recipes: machines, rates, power, exports, byproducts.
sources= node selectors, combinable; omit = whole map: "north", "region:Northern Forest",
"near:@<radius_m>", "node:" (search_resource_nodes lists ids), "grid:X3Y4",
"resource:Crude Oil".
objective: max_mw | max_item | min_raw | min_raw_power | min_machines | min_power.
Omitted: min_raw_power when export_minimums asks for an item, else max_mw. Machine
counts are whole buildings at one derived clock.
exports= whitelist of what may leave, REPLACING the default (omitted: a goalless rate
exports its items on grid power, else power only); [] = only export_minimums, grid power.
Listing "MW" exports power and forbids grid draw: ["MW","Plastic"].
extractor_clocks overclocks source nodes only; clocks spreads a row over more, slower
machines at machine_cost_mw each. Power Shards are not counted.
required= recipes (exact name or class id) that must make their item, excluding their
rivals; a locked one is refused.
save_as= stores the request, never the solution; over an existing plan pass base_rev.
plan= recalls a saved plan and re-solves it.
Unsaved, the answer ends plan="solve:..." for the other plan tools (held until restart).
site_at= with save_as records where the plan stands and measures the water there.
Inputs: plan, save, as_of, limit, +31 more.
plan_from_factoryB
Save a plan mirroring a named factory as built, to edit or extend.
Recipes pinned, inputs supplied, surplus exported (sunk under the flow stance); an unedited equal plan is reused. Differences from the build go in the notes.
Inputs: factory (required), save, as_of, world, +1 more.
plan_layoutBRead-onlyIdempotent
Plan to schematic: blocks, buses, floors, materials, space budget; no coordinates or belt routing (site_plan places it).
The belt/pipe tier is solved with, so schematic and plan agree.
Inputs: plan (required), save, show, as_of, +8 more.
plansARead-onlyIdempotent
List this world's saved plans (version, last change, world moved?), or one plan's versions with name=.
With name=, show='request' prints the stored arguments, what the selectors resolved to and the siting, solving nothing; a forgotten plan is found too. Pass the version (v14 -> base_rev=14) to any tool that changes the plan; edit_plan renames, forgets, undoes, restores.
Inputs: name, save, show, as_of, +3 more.
power_reportBRead-onlyIdempotent
Grid generation capacity vs machine draw, nameplate and measured, and what is free now.
Nameplate: everything built running at once. Measured: each machine weighted by its 300 s productivity window. Generation is capacity on both, except a generator out of fuel or water whose monitor read zero is listed starved: those MW will not arrive.
Inputs: save, as_of, world, biomass.
propose_factoriesARead-onlyIdempotent
Proposed factories: what is built, clustered by slabs, proximity, belts, shared products and supply.
Errs toward splitting: never merges two factories, may return one in pieces. The # column is the proposal: selector other tools take, numbered over all proposals so paging does not shift it. Name one with edit_factory. unnamed_only=true answers 'what have I built and not named'.
Inputs: save, as_of, limit, world, +3 more.
rank_build_sitesARead-onlyIdempotent
Rank fields for a new extraction site of one resource, best first.
Scores untapped reachable capacity against spread, distance to your buildings, purity
and terrain; every raw component is shown to re-weight, the score is a start, not a
verdict. sources= narrows the area with search_resource_nodes' selectors; omit for the
whole map. No offset: raise limit or narrow sources.
Inputs: resource (required), save, as_of, limit, +2 more.
rank_unlocksBRead-onlyIdempotent
Value of each locked alternate recipe to THIS plan: re-solve with it added and report the delta in the plan's own units.
A zero delta is an answer. Deltas are an upper bound: a candidate needing an unbuilt machine is judged as if built, and the machine is named. Alternates on a pending hard drive are flagged as claimable now.
Inputs: plan (required), save, as_of, limit, +2 more.
recipe_detailCRead-onlyIdempotent
One recipe's exact numbers: in/out per minute, machine, cycle, power, unlock source.
Inputs: recipe_id (required), save, as_of, world.
researchARead-onlyIdempotent
HUB milestones or MAM research: what is left, what it costs, what spendable stock affords now.
HUB: READY is about the bill; a tier the Space Elevator has not opened shows the phase
that opens it (phase_requirements). MAM rows marked LOCKS gate a capability (Depot,
Power Augmenter, Somersloop amplification), not a recipe. tier= is HUB only.
Inputs: save, show, tier, tree, +5 more.
search_conduitsARead-onlyIdempotent
Belt and pipe runs near a place or between two areas: both ends, length, elevation, what each end connects to.
A run is one belt chain (split at splitters, mergers and machines) or one placed pipe;
longest first; its id (chain:, pipe:) is a place every tool takes. Proximity is
measured against the drawn line, so a run crossing mid-span counts. show=networks
lists each fluid network instead (fluid, pipe length, centre, what it ends on), distance
from near=; network=N lists its pipes.
Inputs: near (required), to, save, show, +8 more.
search_itemsCRead-onlyIdempotent
Find items by name: form, MJ and sink points.
Inputs: query (required), limit, offset.
search_recipesBRead-onlyIdempotent
Search recipes by name, or by what they consume/produce; marks HAVE/LOCKED against the save.
consumes= is the reverse lookup (every recipe that eats an item); with produces=
too, only recipes doing both. The header counts every recipe_kind over the whole table,
whatever recipe_kind shows.
Inputs: save, as_of, limit, query, +7 more.
search_resource_nodesARead-onlyIdempotent
Resource nodes as fields (clusters within 200 m, by yield), nodes (one row each) or nearest (by distance from near=).
sources= is a list of node selectors; locations union, filters intersect; omit for
the whole map: north|south|east|west|northeast|..., region:, grid:X3Y4,
node:, pin:, near:@<radius_m>, bbox:x1,y1,x2,y2 (metres),
resource:, purity:, kind:; all in a filter means no filter. Printed
node_ids are reusable as node:. Water has no nodes: asking for it lists fracking
satellites, the bodies already pumped and sea level.
Inputs: kind, near, save, show, +9 more.
select_machinesARead-onlyIdempotent
Preview which machines a selector picks, before naming them with edit_factory.
Run it first on product: terms, which also pick machines feeding that product inside other sites. slab: answers what stands on a platform, and describes an empty one.
Inputs: select (required), save, as_of, split, +2 more.
settingsAIdempotent
Settings the page and chat share; change one only when the user asks.
stage_headroom: what diff_vs_save and commission_plan stage a plan against when it stores none. biomass: default of every biomass= parameter. payback_hours, overclock_last: what a plan that sets neither follows. The page's Settings tab shares the file and follows a change. Base map types are listed read-only.
Inputs: change.
show_on_mapAIdempotent
Map links centred on a place: this project's map (draws your save) and the public one (vanilla world, nothing built).
'resource:' centres on every node of that resource with its overlays on (Crude
Oil layers confirmed; a wrong token still opens the right place). pin=true also pins
the place for the page as pin:N; mode= picks the local link's base map.
Inputs: at (required), pin, mode, save, +4 more.
site_planADestructive
Record, update or clear where a saved plan stands (origin, yaw, footprint). Nothing is re-solved.
Origin is the footprint centre in metres; yaw is degrees about world Z as the save stores facing; footprint defaults to plan_layout's square for the largest floor, and the record says whether it was measured or derived. A siting is a record, not a constraint: re-solving ignores it, save_as over the same name keeps it. Once sited, recalls print it, diff_vs_save adds an approximate on-pad census, show_on_map at='plan:' centres on it.
Inputs: plan (required), at, save, as_of, +6 more.
trace_upstreamARead-onlyIdempotent
What feeds a machine, factory or building type, or what it feeds, walked on the save's connections.
factory_query show=links answers this between named factories; this walks from one seed, e.g. which feed can be repiped without dropping the generators behind it. Direction is read from connector roles or the machine's nature; an edge with neither is walked both ways, so a feeder may be over-reported, never missed. Belts and pipes are walked through, not listed; a note names the runs crossed by the chain:/pipe: ids search_conduits takes.
Inputs: seed (required), save, as_of, limit, +2 more.
ui_contextAIdempotent
What the web page has open; call first when the user says 'this', 'here' or quotes an ask: or pin: id.
Names the page's view, plan and version, tab and selection, whether the page reads the same save as you, queued asks, advisories (adv: ids), and every plan version or chat solve by someone else since your last look. Listed asks are marked seen on the page; pass answered= once answered. dismissed= hides an advisory, only when the user asks.
Inputs: save, world, answered, dismissed.
unlocked_recipesCRead-onlyIdempotent
Recipes this world has unlocked; alternates only unless only_alternates=false. Paged by offset=.
Inputs: save, as_of, limit, world, +2 more.
whereamiBRead-onlyIdempotent
Where the player stands, and the nodes, buildings and cave around them.
Position is the save's, so an autosave can be minutes stale. near:me@<radius_m> as a
source selector plans around here.
Inputs: save, as_of, limit, world, +1 more.
world_summaryBRead-onlyIdempotent
One-screen overview of a world: progress, power, problems and advisories (adv: ids).
Inputs: save, as_of, world, biomass.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 49 tools
Most tools are clearly differentiated by detailed descriptions, but several related clusters blur at the edges, e.g. factory_map/propose_factories/factory_sites and plan_factory/plan_from_factory/plans. An expert agent can usually select correctly after reading, but the cognitive load is high enough to risk occasional misselection.
All tool names consistently use snake_case and are readable. The convention is not strictly verb_noun throughout, since noun-only tools like inventory, crates, plans, and bom mix with verb-led names, but the deviations are minor.
At 49 tools, the surface is far above the 3-15 well-scoped range and squarely in the rubric's 25+ 'too many' band. Even for a deep Satisfactory planning domain, this many tools create significant selection overhead and should be consolidated into narrower groups.
Coverage is broad across planning, factories, recipes, resources, inventory, research, power, and map views, with few obvious dead ends for core workflows. Minor gaps remain around vehicle/train logistics and direct build/dismantle actions, but the main domain lifecycle is well supported.
Maintenance
Related MCP Connectors
A MCP server built for developers enabling Git based project management with project and personal…
MCP server for generating rough-draft project plans from natural-language prompts.
An MCP server for deep research or task groups
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server for managing recipes, meal plans, shopping lists, and more through a self-hosted Mealie instance.1MIT
- AlicenseNot gradedqualityDmaintenanceAn external MCP server for diagnosing Minecraft servers via backup analysis, local runtime, or Docker runtime, offering tools for plugin inspection, log analysis, configuration linting, and performance diagnostics.1MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server providing tools for YouTube search, AI trip planning, notes management, web search, and product price comparison, backed by a FastAPI backend.-
- AlicenseNot gradedqualityDmaintenanceMCP server for Minecraft that manages map points, provides recipes and guides, and enables inspection/download of files and worlds via the exaroton REST API.MIT
A power plant up close: machines, belts, pipes, wires
The terrain map, shaded from the game's heightfield