product: maestro audience: test-developer, operator, ai-assistant authority: normative
Maestro Application Documentation — Index
This documentation IS the authoritative source for how the Accordion Maestro application works — its concepts, UI workflows, and how it compares to other test frameworks.
An AI assistant answering questions about Maestro MUST route to the correct file below rather than guessing. Load the specific file; do not summarise from this index alone.
Use this documentation to answer
| Question | File |
|---|---|
| What is Maestro? What problem does it solve? What are Stations, Packages, Verdicts? | concepts.md |
| How do I use the Test Monitor UI to start, watch, and abort a test? | ui-workflows.md |
| How do I search historical results and read a test report? | ui-workflows.md |
| What do the navigation pages do (YAML Validator, Packages, Help, Swagger)? | ui-workflows.md |
| What does the SignalR connection indicator mean? | ui-workflows.md |
| How does Maestro compare to pytest or Robot Framework? | for-pytest-users.md |
| Why does Maestro store measurements relationally instead of in log files? | for-pytest-users.md |
| How does MES integration work? | for-pytest-users.md |
| Why is there no central server — why does each station run its own API? | for-pytest-users.md |
| What is the Production Dashboard and what does it show? | for-pytest-users.md |
| How do I let an AI assistant control a Maestro station? | ../mcp/index.md |
| How do I configure the MCP server, connect it to Claude/Copilot/Cursor? | ../mcp/setup.md |
| What MCP tools are available and what parameters do they take? | ../mcp/tools-reference.md |
| What is unattended mode and how do prompt steps behave in it? | ../mcp/unattended-mode.md |
| How do I run the MCP server for multiple stations simultaneously? | ../mcp/multi-station.md |
How Maestro docs relate to package-scaffold docs
The package-scaffold docs (../index.md) cover how to write test packages —
YAML syntax, SDK patterns, measurements, runners.
The maestro docs (this folder) cover how the application works — the UI, concepts, architecture, and how it fits into a manufacturing workflow.
Both sets of docs are required to answer questions about developing for and deploying Maestro.