Business MCP Server

MCP server for Microsoft Dynamics 365 Business Central -- speaks BC's native WebSocket protocol directly. The business mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

Give AI assistants direct access to Microsoft Dynamics 365 Business Central.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Its toolset

Everything the assistant can do here goes through one of these:

• macOS — ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows — %APPDATA%\Claude\claude_desktop_config.json
• Linux — ~/.config/Claude/claude_desktop_config.json
• Card — style** (header on Card pages, factbox, requestPage): fields[] and (for header) actions[]
• List — style** (lines on Documents, header on List pages, repeater subpages): rows[] and totalRowCount
• Auto — dismisses license popups on fresh databases
• Property — Value
• Language — TypeScript / Node 20+
• Auth — NavUserPassword (OAuth on roadmap)
• Tools — 12
• Tests — 284 unit/protocol + 111 integration
• Variable — Required

Configuration

You will need 5 environment variables: BC_BASE_URL, BC_USERNAME, BC_PASSWORD, BC_TENANT_ID, BC_APPLICATION_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Business.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the business mcp server does with a few real requests.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Business's toolset — macOS, Windows, Linux and 11 more — is a fair guide to whether it matches your workflow. It is maintained by sshadows; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Business's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.