From origo-bc
List every Business Central tenant / environment currently configured in the Cowork MCP config. Use this skill when the user types `/origo-bc-list-environments`, asks which BC environments are connected, which BC tenants Cowork knows about, what `bc-*` MCP servers are registered, or wants to audit their Origo BC setup. Reads the Cowork / Claude Desktop MCP config file and shows a table of every `bc-*` entry with its resolved default company (if any).
How this skill is triggered — by the user, by Claude, or both
Slash command
/origo-bc:origo-bc-list-environmentsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Reads the Cowork MCP config and lists every `bc-*` entry.
/origo-bc-list-environments — Show configured BC tenantsReads the Cowork MCP config and lists every bc-* entry.
Locate the Cowork / Claude Desktop config file:
%APPDATA%\Claude\claude_desktop_config.json~/Library/Application Support/Claude/claude_desktop_config.json~/.config/Claude/claude_desktop_config.jsonParse the JSON and collect every key under mcpServers starting with
bc-.
For each entry, extract:
bc- prefix).args).dpapi:) or raw (plain:).Render a table:
| Nickname | Default company | Auth format | Script path |
|---|---|---|---|
| kappi | AAAA-... | dpapi | ...\OrigoBC\dynamics-is.js |
| cronus | (none) | dpapi | ...\OrigoBC\dynamics-is.js |
If no bc-* entries exist, tell the user and suggest /origo-bc-setup.
dpapi: / plain: blob itself. Only report its
length and format prefix.If the user explicitly asks ("which companies are in each?"), you may
call mcp__bc-<nickname>__list_companies per entry to show the resolved
companies. Don't do that by default — it hits the network and spins up the
proxy for every tenant.
npx claudepluginhub businesscentralal/origo-bc-plugin --plugin origo-bcCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.