How mirzatheduck/multi-agent-telemetry-hub works
This is a multi-agent assistant for personal telemetry and game-code analysis. A user submits a task through the CLI; the orchestrator plans and routes it to telemetry and/or code-analysis agents, then the DB bridge validates and persists their results. The product also exposes its MCP tools to external clients and supports querying stored data. The graph reflects README-documented flows and shown source references; unsampled implementation details are omitted where call relationships cannot be verified.
Main entry points: orchestrator.py Task orchestrator · db_bridge_agent.py DB bridge agent · base.py Tool registry · mysql_mcp_tool.py MySQL tools
Components 19
User Interface
- CLI entry
main.py - Event renderer
cli/renderer.py
Agent Workflow
- Task orchestrator
agents/orchestrator.py - Model router
config/settings.py - GameDev agent
agents/gamedev_agent.py - Telemetry agent
agents/telemetry_agent.py - DB bridge agent
agents/db_bridge_agent.py - Agent plumbing
agents/base.py
MCP Tools
- MCP stdio server
mcp_tools/server.py - Tool registry
mcp_tools/base.py - Code and file tools
mcp_tools/system_stats_tool.py - MySQL tools
mcp_tools/mysql_mcp_tool.py
Persistence
- Schema and CRUD
database/crud.py - Database facade
config/database.py - MySQL store
- In-memory store
config/database.py
Other components
- User
- MCP client
- Model providers
Connections 23
- User → CLI entry: submits task
README.md - CLI entry → Task orchestrator: runs pipeline
README.md - CLI entry → Event renderer: renders events
main.py - Task orchestrator → Model router: selects models
agents/orchestrator.py - Task orchestrator → GameDev agent: dispatches analysis
agents/orchestrator.py - Task orchestrator → Telemetry agent: dispatches parsing
agents/orchestrator.py - Task orchestrator → DB bridge agent: dispatches persistence
README.md - GameDev agent → DB bridge agent: passes analysis JSON
README.md - Telemetry agent → DB bridge agent: passes telemetry JSON
README.md - Task orchestrator → DB bridge agent: passes execution history
README.md - Agent plumbing → Model router: requests completion
agents/base.py - Agent plumbing → Tool registry: calls tools
agents/base.py - GameDev agent → Code and file tools: calls analysis tools
README.md - DB bridge agent → MySQL tools: calls write tools
agents/db_bridge_agent.py - MCP client → MCP stdio server: sends JSON-RPC
README.md - MCP stdio server → Tool registry: dispatches calls
mcp_tools/server.py - Tool registry → Code and file tools: registers tools
mcp_tools/__init__.py - Tool registry → MySQL tools: registers tools
mcp_tools/__init__.py - MySQL tools → Schema and CRUD: validates table rows
mcp_tools/mysql_mcp_tool.py - MySQL tools → Database facade: reads and writes
mcp_tools/mysql_mcp_tool.py - Database facade → MySQL store: uses when configured
config/database.py - Database facade → In-memory store: falls back to
config/database.py - Model router → Model providers: calls providers
config/settings.py