aoa-config-doctor

To diagnose missing MCP server connections, run a workspace configuration check that verifies expected MCP names against the active workspace root and returns exactly what is missing. This identifies whether the failure is a discovery issue or an MCP wiring fault.

The /mcp list looks incomplete during agent startup when shared launcher skills are miswired or MCP server connections fail to resolve. Running a diagnostic check validates the workspace root context and isolates the missing dependencies causing the incomplete load.

Fix missing or disconnected shared launcher skills by identifying the exact first path to repair. The diagnostic process checks workspace-aware validators, confirms whether the fault is skill discovery or wiring, and outputs actionable path-first repairs to restore capabilities.

You can validate workspace configuration before agent startup failures by checking that expected MCP names and skill metadata are present and correctly wired. This workspace-aware validation suggests the smallest local validators already present to reduce guesswork.

A skill discovery fault means the workspace cannot find the expected skills or metadata, while an MCP wiring issue means the connections to MCP servers are broken. The diagnostic check distinguishes between the two and returns the specific fault type.

When skill metadata looks wrong or dependencies do not resolve, run a diagnostic to verify the active workspace and check expected MCP names. It returns what is missing and provides the exact first path to fix the discovery or wiring fault.