origo-bc-switch-company

Update a Cowork MCP bc-<nickname> config to a new Business Central company GUID.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/businesscentralal/origo-bc-plugin --skill origo-bc-switch-company
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: origo-bc-switch-company
Source: https://github.com/businesscentralal/origo-bc-plugin/tree/main/plugins/origo-bc/skills/origo-bc-switch-company
Command: npx skills add https://github.com/businesscentralal/origo-bc-plugin --skill origo-bc-switch-company

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of needing to retarget an existing Cowork MCP configuration entry to a different Business Central company GUID without recreating credentials or connection blobs.

Core Features & Use Cases

  • Retarget existing bc-* entries: Updates only the company GUID argument for an existing bc-<nickname> MCP server.
  • Guided company selection from your tenant: Lists available companies from Business Central via mcp__bc-<nickname>__list_companies, then validates the selected GUID against that result set.
  • Safe, minimal config change: Writes the MCP config atomically (temp file + rename), never touches the encrypted connection blob, and instructs the user to restart Cowork.

Quick Start

Ask the system to run /origo-bc-switch-company to update the default company for one of your existing bc-<nickname> entries to the company you select.

Frequently Asked Questions about origo-bc-switch-company

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

FAQPage Schema
How do I switch the default company in a Business Central MCP configuration?

Switching the default company in a Business Central MCP configuration involves updating the company GUID argument in an existing Cowork MCP server entry. The process validates the selected GUID against your tenant's available companies before applying the update.

Can I retarget a bc-* MCP entry without recreating credentials?

Yes, you can retarget a bc-* MCP entry without recreating credentials. The process updates only the company GUID in the Cowork MCP config and never touches or decrypts the stored connection blob.

How does tenant discovery work when changing Business Central companies?

Tenant discovery for changing Business Central companies works by calling the list_companies function to enumerate available companies from your tenant. The skill uses this list to validate your selected company GUID before atomically rewriting the MCP configuration.

What is the safest way to update a Cowork MCP config to use a new company GUID?

The safest way to update a Cowork MCP config with a new company GUID is to write the configuration atomically using a temporary file and rename operation. This method ensures the config is never left in a corrupted state if the update fails.

Do I need to restart Cowork after changing the Business Central company GUID?

Yes, you need to restart Cowork after changing the Business Central company GUID. The skill updates the configuration file atomically but requires a manual restart to apply the new default company mapping to the MCP server.