origo-bc-add-env

/origo-bc-add-env — Add another BC tenant / environment

Adds a new bc-<nickname> entry to the Cowork MCP config using the scripts already installed under %USERPROFILE%\OrigoBC\. Does not reinstall scripts; if that folder is missing, redirect the user to /origo-bc-setup instead.

Preconditions

Before doing anything:

1. Node.js 18+ must be on PATH. Run node --version; abort if the command fails or reports a major version below 18. Cowork launches each bc-* entry as node <path>\dynamics-is.js ..., so there is no point adding a broken entry. Tell the user:

   I can't add another BC environment without Node.js 18+. Install it from https://nodejs.org/ (LTS is fine), open a new Cowork session so PATH refreshes, then re-run /origo-bc-add-env.

2. %USERPROFILE%\OrigoBC\dynamics-is.js exists. If it doesn't, stop and tell the user:

   It looks like Origo BC has not been set up on this machine yet. Run /origo-bc-setup first.

What this command does

1. Confirm %USERPROFILE%\OrigoBC\ is already populated.
2. Ask (via AskUserQuestion, one at a time):
   • Short nickname (must be unique vs. existing bc-* entries).
   • Tenant ID, client ID, environment.
   • Optional default company GUID.
3. Print the helper command for the user to run in their own terminal (Create-PlainConnectionString.ps1 on Windows, create-connection-string.js elsewhere) with the tenant / client / environment pre-filled.
4. Receive the pasted dpapi: / plain: blob.
5. Append a new bc-<nickname> entry to the Cowork MCP config.
6. Prompt the user to restart Cowork and verify with mcp__bc-<nickname>__list_companies.

Uniqueness check

Before asking for the nickname, read the current MCP config and list the existing bc-* keys back to the user as forbidden values. If the user's chosen nickname collides, ask again.

Guardrails

Same as /origo-bc-setup:

• Never prompt for the client secret in chat.
• Never transmit the blob anywhere other than the local config file.
• Atomic write of the config (temp file + rename).

Step-by-step

Step 1 — Verify Node.js and the existing install

node --version   # must exit 0 and report v18+ (v18/v20/v22 LTS all fine)
test -f "$USERPROFILE/OrigoBC/dynamics-is.js" && echo OK

If either check fails, stop and redirect the user (Node → https://nodejs.org/; missing install → /origo-bc-setup).

Step 2 — List existing entries

Read %APPDATA%\Claude\claude_desktop_config.json, enumerate keys under mcpServers that start with bc-, and show them to the user so they can pick a non-colliding nickname.

Step 3 — Collect coordinates

Use AskUserQuestion for: nickname, tenant, client, environment, optional default company GUID.

Step 4 — Generate the blob

Windows:

cd $env:USERPROFILE\OrigoBC
.\Create-PlainConnectionString.ps1 `
  -TenantId    '<tenant>' `
  -ClientId    '<client>'