arc-world-engine-mcp
Related Servers
Alternatives to arc-world-engine-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceConnects any MCP client to a deterministic in-browser Docker simulation so a user's own AI can teach by inspecting and mutating world state, rewinding and comparing events, running 27 "what-if" experiments, tracing concept relationships, and quizzing the learner. It exposes 14 typed tools over Streamable HTTP with bearer-token auth, needing no hosted AI or server-side lab state.MIT
- AlicenseNot gradedqualityAmaintenanceEnables an AI assistant to build and revise an explicit shared world model, then reason, create, narrate, remember, and give writing feedback through inspectable processes, concepts, and cuts. Supports general-purpose modeling, storytelling, agent/user memory, and ideation over one engine and graph while keeping estimates, interpretations, and observations distinct.MIT
- AlicenseNot gradedqualityBmaintenanceEnables LLM agents to inhabit a shared simulated world where they can move, communicate, trade, leave signs, and try to survive under deterministic, data-driven rules that can be changed at runtime while spectators observe events and state.3 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to interact with the Blocksworld Simulation to perform block manipulation actions, query real-time state, and verify multi-step plans. It bridges the Model Context Protocol with the simulation's REST API for AI planning research and agent development.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to run and manage a worldview-agnostic interactive fiction engine, including world initialization, deterministic action resolution, SillyTavern card and lorebook imports, narration context, state tracking, and recaps.1MIT
- FlicenseNot gradedqualityBmaintenanceProvides tools to inspect, edit, run, replay, compare, and provide feedback on physics-based marble simulations, returning structured results and PNG captures.-
TDQS
Scored across 18 tools
Most tools have clear, distinct purposes, such as creating/updating/removing actors, adding effects by trigger type, and managing snapshots. The only minor overlap is between the general add_rule and the specific add_*_effect tools, but descriptions clarify their scopes.
Tool names mostly follow a consistent verb_noun snake_case pattern (create_actor, update_actor, remove_actor, add_rule). Minor deviations include merge_actors using plural while other actor operations are singular, and rollback lacking a noun object.
18 tools is on the higher side but each addresses a distinct aspect of the world engine: world setup, actor management, simulation, effects, and state inspection. No tool seems redundant, and the count is appropriate for the complex domain.
The tool surface covers the full lifecycle of world management: creating worlds, loading static maps, actor CRUD, simulation, rule/effect binding, observation comparison, and snapshot rollback. There are no obvious gaps that would prevent an agent from completing common tasks.