skills.rest
businesscentralal
businesscentralalOFFICIAL
Explore all skills by this author →
WebsiteGitHub

origo-bc-update-env

Regenerate encrypted AES-256-GCM connection blobs for bc-* entries in Cowork MCP config.

Updated Apr 21, 2026
Search Tags:#environment setup#credential rotation#aes-256-gcm#business central#mcp config#connection blob#device code
One-click install
npx skills add https://github.com/businesscentralal/origo-bc-plugin --skill origo-bc-update-env
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: origo-bc-update-env
Source: https://github.com/businesscentralal/origo-bc-plugin/tree/main/plugins/origo-bc/skills/origo-bc-update-env
Command: npx skills add https://github.com/businesscentralal/origo-bc-plugin --skill origo-bc-update-env

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It fixes broken or outdated Business Central connection entries by re-generating the encrypted connection blob and patching the existing Cowork MCP config entry without unsafe clipboard hand-offs.

Core Features & Use Cases

  • Replaces an existing bc- environment entry*: updates the selected entry (including its default company GUID) while leaving other entries untouched.
  • Supports key remediation scenarios: handles legacy plaintext-to-AES migration, credential rotation, refresh token expiry, environment changes, and auth method switching (client secret vs device code).
  • End-to-end validation before writing config: validates new credentials via an internal round-trip (list_companies) before replacing the config entry.
  • Cross-platform generation: uses PowerShell on Windows and a Node helper on macOS/Linux to produce and replace the connection blob.

Quick Start

Ask: Update my existing BC connection with /origo-bc-update-env so the stored credentials are re-encrypted and the selected bc-* entry is replaced after validation.

Frequently Asked Questions about origo-bc-update-env

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix a broken Business Central connection after a refresh token expires?▼

To fix a broken Business Central connection after token expiry, you regenerate the encrypted AES-256-GCM connection blob for the existing bc-* entry and atomically replace the outdated MCP config.

Can I switch my Business Central authentication from client secret to device code?▼

Yes, you can switch Business Central authentication from client secret to device code by selecting the target bc-* entry, providing the new auth method inputs, and validating credentials before updating the configuration.

What is the best way to migrate legacy plaintext Business Central credentials to AES-256-GCM?▼

The best way to migrate legacy plaintext Business Central credentials to AES-256-GCM is to re-run the environment setup to generate an encrypted connection blob and replace the vulnerable config entry securely.

Does updating a bc-* environment entry leave my other MCP config connections untouched?▼

Yes, updating a bc-* environment entry leaves your other MCP config connections untouched by atomically replacing only the selected target entry after validating the new credentials via list_companies.

How do I safely rotate credentials for a Business Central environment without exposing secrets in chat?▼

To safely rotate credentials without exposing secrets in chat, the process collects tenant, client, and environment inputs interactively, generating the new connection blob via PowerShell or Node without displaying the secret values.

Why does my Business Central connection validation fail before the config entry is replaced?▼

Business Central connection validation fails before replacement if the new credentials cannot complete an internal round-trip check using list_companies, ensuring only working credentials are written to the config.

Related Skills

Explore More Software Engineering Skills→
businesscentralalbusinesscentralal

origo-bc-add-env

Add a Business Central tenant entry to an Origo BC Cowork MCP config with encrypted credentials.

Official
Advanced
businesscentralalbusinesscentralal

origo-bc-setup

Automate Business Central connection setup by collecting tenant details and configuring MCP entries.

Official
Advanced
AllBeingsFutureAllBeingsFuture
9

run-shell

Execute shell commands with configurable working directory and timeout.

Community
Intermediate
DevelopersCoffeeDevelopersCoffee
3

cwe-311-non-encrypted-storage

Remediate CWE-311 vulnerabilities in Java code with AES-256-GCM encryption.

Official
Intermediate