Back to blog

Introducing bc-mcp-proxy: a free, open-source MCP server for Business Central

Stephane Vangelder · ·
launch MCP Business Central open-source

We open-sourced our Microsoft Business Central MCP proxy under MIT. Install it with one pip command, point Claude Desktop at it, and ask your tenant anything.

Today we’re open-sourcing bc-mcp-proxy — the small piece of plumbing that lets any AI client (Claude Desktop, Cursor, VS Code) talk to Microsoft Dynamics 365 Business Central over the Model Context Protocol.

github.com/360solutionsbe/bc-mcp-proxy · MIT License · pip install 360solutions-bc-mcp

What it is

A stdio-to-HTTP bridge. Your AI assistant speaks stdio MCP locally; Business Central exposes an HTTP MCP endpoint. The proxy translates between the two and handles OAuth so you don’t paste tokens into config files.

In practice, that means you can open Claude Desktop and ask things like:

“Show me the top 10 customers by outstanding balance, and flag anyone who’s gone past 60 days.”

…and get the answer from your live BC data, not a copy-pasted CSV.

Why we open-sourced it

We’ve been building MCP servers for clients for the past year. The Business Central one kept getting reinvented in slightly different ways every time. Open-sourcing the proxy means:

  • Customers don’t pay for plumbing. They pay us for the apps and integrations on top.
  • It survives us. Anyone can fork, audit, or maintain it. MIT — no strings.
  • The community improves it. A spec churn or a BC version change becomes a PR, not a 360-only problem.

It’s the same calculus a lot of small ISVs make on infrastructure code, and it’s the right one for protocol bridges specifically.

Try it in 20 minutes

You need:

  • A Microsoft Dynamics 365 Business Central tenant (online or sandbox)
  • An Azure App Registration with BusinessCentral.ReadWrite.All delegated permission
  • A working Claude Desktop, Cursor, or VS Code MCP client
pip install 360solutions-bc-mcp
python -m bc_mcp_proxy setup

The setup wizard walks you through Azure App Registration, the BC MCP Configuration page, and produces a Claude Desktop config snippet you can paste into %APPDATA%\Claude\claude_desktop_config.json.

For the full hands-on walkthrough — Azure portal screenshots, OAuth scope choices, troubleshooting — see the BC MCP setup guide.

Microsoft is shipping a first-party BC MCP server too

It’s worth saying out loud: Microsoft announced a first-party BC MCP server in BC 2025 wave 2 (BC27.1). Their server and ours are not direct substitutes — they target different deployment topologies and customisation models. We’ll publish a head-to-head positioning piece next week.

For most customers reading this today, two things are true:

  1. The Microsoft server isn’t generally available yet.
  2. When it is, our proxy stays useful for environments where you need multi-tenant routing, custom auth flow, on-premise BC, or a different deployment posture than Microsoft’s hosted offering.

What’s next

  • Day +7: “Microsoft’s BC MCP Server vs bc-mcp-proxy: when to use which”
  • Day +14: the full backstory — why we chose MIT, what we left out
  • Day +21: Static vs Dynamic mode trade-offs (a technical deep-dive)
  • Day +28: Five setup pitfalls we already hit, with the actual error strings

If you want those when they land, subscribe to the newsletter. One email, no spam, unsubscribe in one click.

If you want to try the proxy and get stuck — the guide covers the common failure modes, or book a 30-minute discovery call and we’ll walk you through it. Free.