How myers404/demo-engine works
Demo Engine interprets YAML-defined state, schemas, and tool actions. Its main workflow is to load and validate a demo definition, create in-memory session state, execute a requested tool against a copy of that state, validate the result, and return the new state and result. The MCP adapter exposes configured tools over stdio and commits state only after successful execution. The engine is concentrated in one source file, so several nodes represent distinct responsibilities within that file; the graph does not assume persistence or multi-user hosting.
Main entry points: engine.py Tool Executor · mcp_server.py MCP Server · commerce_demo.yaml Demo YAML
Components 13
Demo Definition
- Demo YAML
examples/commerce_demo.yaml - Config Loader
src/demo_engine/engine.py
Execution Engine
- Schema Validation
src/demo_engine/engine.py - Session State
src/demo_engine/engine.py - Tool Executor
src/demo_engine/engine.py - Action Interpreter
src/demo_engine/engine.py - Collection Selector
src/demo_engine/engine.py - Reference Resolver
src/demo_engine/engine.py
MCP Runtime
- MCP Server
src/demo_engine/mcp_server.py - Tool Registry
src/demo_engine/mcp_server.py - stdio Transport
src/demo_engine/mcp_server.py
Other components
- Python Caller
- MCP Host
Connections 17
- Demo YAML → Config Loader: defines config
README.md - Python Caller → Config Loader: loads config
README.md - Config Loader → Schema Validation: validates schemas
src/demo_engine/engine.py - Python Caller → Tool Executor: executes tool
README.md - Tool Executor → Schema Validation: validates input and state
src/demo_engine/engine.py - Tool Executor → Session State: copies and updates
src/demo_engine/engine.py - Tool Executor → Action Interpreter: runs action
src/demo_engine/engine.py - Action Interpreter → Collection Selector: selects matches
src/demo_engine/engine.py - Action Interpreter → Reference Resolver: resolves values
src/demo_engine/engine.py - Tool Executor → Reference Resolver: resolves result
src/demo_engine/engine.py - Tool Executor → Schema Validation: validates output
src/demo_engine/engine.py - MCP Host → stdio Transport: connects over stdio
README.md - stdio Transport → MCP Server: routes MCP requests
src/demo_engine/mcp_server.py - MCP Server → Config Loader: loads definition
src/demo_engine/mcp_server.py - MCP Server → Tool Registry: lists configured tools
src/demo_engine/mcp_server.py - MCP Server → Tool Executor: executes tool calls
src/demo_engine/mcp_server.py - MCP Server → Session State: commits next state
src/demo_engine/mcp_server.py