origo-bc-add-env

To add a new Business Central environment to an existing Cowork MCP configuration, run the add-env command and provide a unique nickname plus tenant, app, environment, auth, and company inputs. It generates an encrypted credential blob and validates the connection via list_companies before atomically writing the config file.

Before adding a Business Central tenant to Cowork MCP, you need Node.js 18+ installed and the local OrigoBC helper scripts already present on your machine. The setup is platform-aware and handles execution paths across Windows, macOS, and Linux without reinstalling underlying helpers.

Adding a Business Central environment does not require reinstalling local helper scripts. The process reuses already-installed local OrigoBC scripts and safely extends your existing MCP configuration by adding a new bc-nickname entry with validated credentials.

Credentials are secured when configuring a Business Central tenant entry by generating an encrypted credential blob using DPAPI and AES wrapping. Safety guardrails prevent exposing secrets in chat, avoid inspecting or decrypting existing blobs, and perform atomic BOM-correct config writes to prevent broken MCP entries.

Business Central environment configuration validation fails when the list_companies workflow cannot verify the generated encrypted credentials against the server. The skill performs this end-to-end validation step before writing the config to ensure the tenant, app, and auth inputs are correct and prevent broken MCP entries.

You can connect Cowork MCP to multiple Business Central companies using device code auth by adding separate bc-nickname entries for each environment. The interactive collection process gathers tenant, app, environment, auth, and company inputs, then validates each set via list_companies before committing the config.