origo-bc-list-environments

Listing configured Business Central tenants involves parsing the MCP config file and enumerating every mcpServers entry prefixed with bc-. The Skill extracts each entry's nickname and default company to support environment audits and troubleshooting.

Auditing Business Central environments safely requires read-only JSON parsing that identifies whether the stored auth blob is dpapi-wrapped or AES ciphertext, while never printing the connection blobs to ensure secrets remain protected.

To check the default company for bc-* MCP servers, the Skill reads the MCP config file and extracts the default company GUID from each mcpServers entry prefixed with bc-, returning the resolved configuration details.

When no bc-* entries are found in the Cowork MCP config, the Skill provides robust reporting and guides you toward the setup flow instead of leaving you guessing, ensuring proper onboarding and configuration troubleshooting.

You can audit Business Central tenants even with a malformed config file because the Skill provides robust reporting when the config file is missing or malformed, ensuring safe handling during environment discovery.

Yes, the environment audit supports both dpapi-wrapped and AES ciphertext authentication blobs. The Skill resolves and reports whether each stored auth blob is dpapi-wrapped or AES ciphertext during the read-only configuration parsing.