gto-recipe-mcp
Related Servers
Alternatives to gto-recipe-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables querying a live Satisfactory game through Ficsit Remote Monitoring to answer questions about production, power, logistics, and factory health.MIT
- FlicenseNot gradedqualityBmaintenanceProvides MCP tools to query Factorio recipes, technologies, and save progress, including search, production chain analysis, and plan validation against a specific save's research and enabled recipes.-
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to query a running KanColle game client's live state and integrated resources—fleets, quests, battle history, and id lookups—through read-only tools.14 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables read-only querying of a local SQLite database via MCP, with tools to list tables, retrieve schema, and execute SELECT/WITH/EXPLAIN queries.-
- FlicenseNot gradedqualityBmaintenanceEnables MCP clients to query a live Factorio 2.0 world through bounded read-only operations covering spatial, inventory, resource, and diagnostic data over loopback RCON.1-
- FlicenseNot gradedqualityDmaintenanceEnables managing recipes via a web UI and MCP tools, allowing retrieval and saving of recipe data through natural language.-
TDQS
Scored across 12 tools
Most tools target distinct queries (recipe, producers, consumers, machine, material, me_parts). Some conceptual overlap exists: trace (upstream/downstream tree) relates to producers/consumers (flat lists), and balance vs balance_v differ only by added voltage, though detailed descriptions clearly delineate them.
All names use consistent lowercase snake_case, which is readable and predictable. Minor deviations exist: singular/plural mix (machine vs machines_for), a _for suffix, and the balance/balance_v abbreviation, but no chaotic mixing of conventions.
12 tools sit comfortably in the ideal 3-15 range. Each tool exposes a distinct capability (search, lookup, relationship tracing, balancing, planning) that earns its place for a complex recipe-mod domain.
The surface covers the recipe lifecycle well: search, recipe detail, producers/consumers, machine and material definitions, tracing, material balancing, production-line planning, and ME parts. Coverage is broad for the domain; only niche gaps (e.g. dedicated item/ore lookups) remain, which search can partially handle.