minmo-doctor-mm

Run the dependency doctor to diagnose all minmos-harness plugin dependencies at once. It executes a comprehensive sweep covering MCP servers, environment variables, project files, external plugins, build environment, and Pub/Sub configuration.

The best way to check MCP server and environment readiness is running a comprehensive dependency diagnosis. It enforces a defined checklist to verify all dependencies are properly registered and accessible before plugin release.

Yes, you can use dependency diagnosis output for CI integration and remediation. The doctor generates a structured report suitable for identifying configuration issues and automating checks within your continuous integration pipelines.

Your minmos-harness plugin may fail to access external plugins or Pub/Sub configuration due to unregistered dependencies or misconfigured environment variables. Running a full dependency diagnosis identifies these exact registration and access failures.

Yes, the minmos-harness doctor checks project files and build environment configuration. Its diagnostic scope explicitly covers project files, build environment, MCP servers, environment variables, external plugins, and Pub/Sub configuration.

You should run a minmos-harness dependency check before releasing a plugin to verify all dependencies are properly registered and accessible. It is also useful in development for real-time guidance during configuration adjustments.