The Business Central MCP server is a Microsoft-hosted endpoint, mcp.businesscentral.dynamics.com, that lets Copilot Studio, GitHub Copilot, Claude and other MCP clients call Business Central APIs as the signed-in user. It has been generally available since update 28.0. Out of the box it is read-only; write access exists only where an administrator explicitly allows it per API.

The one-sentence answer

Point any Model Context Protocol client at https://mcp.businesscentral.dynamics.com, sign in with Microsoft Entra ID, and the agent can use exactly the Business Central API pages and queries that both your MCP server configuration and the signed-in user’s permissions allow—read-only by default.

Points clés

  • The Business Central MCP server is a Microsoft-hosted endpoint (https://mcp.businesscentral.dynamics.com) for Business Central online: public preview from update 27.1 in October 2025, generally available since update 28.0 (2026 release wave 1).
  • Without any setup, the built-in default configuration only lets agents discover and read eligible API pages and API queries that the signed-in user is already permitted to use.
  • Write access requires an MCP server configuration with Unblock Edit Tools switched on and Allow Create, Allow Modify, Allow Delete or Allow Actions ticked per API object on the Model Context Protocol (MCP) Server Configurations page (page 8350).
  • Every call runs as the signed-in user via OAuth 2.0 with PKCE against Microsoft Entra ID; Visual Studio Code and Copilot Studio use a Microsoft-preregistered app, while Claude, ChatGPT and GitHub Copilot CLI need your own app registration with the delegated Financials.ReadWrite.All permission.
  • An EU-localised Business Central environment stays in the EU Data Boundary, but rows returned to an external AI host are processed under that host's terms, so choosing the MCP host is a data-protection decision.
  • Microsoft has announced planned charges for Business Central MCP tools without publishing prices; Copilot Studio agents already require a licence with Copilot Credits capacity.

What the Business Central MCP server is

The Model Context Protocol (MCP) is an open standard for how AI applications discover and call tools in other systems. Microsoft runs an MCP server for Business Central online as part of the service: there is nothing to install, and every client uses the same endpoint. The server reads metadata from your environment, turns API pages and API queries into MCP tools, and executes the tool calls an agent makes. Microsoft documents it for Business Central online only.

Keep three roles apart. The agent is the reasoning layer (a Copilot Studio agent, GitHub Copilot in agent mode, Claude). The MCP host is the application that holds the connection and sends tool calls. The Business Central MCP server translates those calls into API operations, under rules you define in Business Central.

1. AI agent

Copilot Studio agent, GitHub Copilot, Claude, ChatGPT

2. MCP host

Streamable HTTP with TenantId, EnvironmentName, Company, ConfigurationName

3. BC MCP server

mcp.businesscentral.dynamics.com selects the configuration

4. Two gates

Allow Read / Create / Modify / Delete / Actions, and the user’s own permission sets

5. BC APIs

API v2.0 pages and queries, API groups, custom AL APIs

Microsoft Entra ID · OAuth 2.0 authorisation code flow with PKCE between steps 2 and 3 · every call runs as the signed-in user

How an agent reaches Business Central data through MCP. The configuration and the user’s permissions both have to allow an operation before it runs.

Status: preview in 27.1, generally available since 28.0

UpdateWhat Microsoft listsStatus
27.1 (2025 wave 2)Connect AI agents to Business Central through MCP serverPublic preview from 31 October 2025
28.0 (2026 wave 1)Create agentic experiences with enhanced MCP server (now from Visual Studio Code and other MCP-compliant clients)General availability
28.0Feature: Enable MCP Server accessNow mandatory; switching it off has no effect
29.0 (2026 wave 2)Run data queries with MCP ServerListed as GA; in 29.1 the setup page says “(Preview/Billable)”

The 29.0 nuance matters. The release overview lists the data query feature as generally available, while the configuration documentation still labels it Data Query Tools (Preview). In a version 29.1 environment the Server Features list goes further and labels it Data Query Tools (Preview/Billable). Treat it as a preview that may be charged for, and switch it on deliberately rather than by default. Do not confuse any of this with the separate Business Central administration center MCP server at /admin/v1, which manages environments rather than company data and has been a production-ready preview since 28.0.

What is exposed, and how you control it

Without any setup, the built-in default configuration (it has a blank name) uses dynamic tool mode with read-only discovery: agents can find and read every eligible API page and API query the signed-in user is allowed to run. Nothing can be created, changed, deleted or posted through it.

Anything beyond that is defined on the Model Context Protocol (MCP) Server Configurations page (page 8350), which requires the MCP - Admin permission set or equivalent. Each configuration has a Name, Description, an Active switch (an active configuration is read-only until you deactivate it) and Unblock Edit Tools, without which no create, modify, delete or action operation is possible.

Model Context Protocol (MCP) Server Configuration page in Business Central 29.1 with the Active, Default and Unblock Edit Tools switches, the Server Features list and the Active System Tools FactBox
An active MCP server configuration in Business Central 29.1: the General switches, the three Server Features (note the “Preview/Billable” label on Data Query Tools), and the Active System Tools FactBox showing the three tools that dynamic tool mode exposes to clients.

API Tools

You curate the API pages and queries with Select APIs, Add All Standard APIs (API v2.0) or Add APIs by API Group for custom AL APIs, then tick the allowed operations per object. Queries are read-only; ListPart and CardPart API pages are not supported.

Dynamic Tool Mode

Replaces individual tools with bc_actions_search, bc_actions_describe and bc_actions_invoke, which helps with limits such as Copilot Studio’s 70 tools. Its Discover Read-Only Objects option (off by default) opens read access to all other eligible APIs.

Data Query Tools (Preview/Billable)

Adds bc_data_find_tables, bc_data_get_table_schema, bc_data_get_table_relations and bc_data_query, so the agent can compile and run read-only AL queries over tables that have no API.

With dynamic tool mode off, each allowed operation becomes a named tool built from API metadata, for example List_Customers_PAG30009, Create_Customer_PAG30009 and Modify_Customer_PAG30009. Use Validate before activating: it flags removed API objects, missing parent pages and entries with Allow Modify but no Allow Read. Set as Default makes a named configuration the one used when a client sends no ConfigurationName; Advanced > Export and Import move configurations between sandbox and production as JSON.

The rule that decides everything

An agent can do only what the configuration allows and what the signed-in user may do in Business Central. A user with posting rights plus a configuration that allows actions on sales invoices gives the agent a posting tool. Least privilege therefore starts with the user’s permission sets, not with the prompt.

How each AI client connects

MCP hostEntra appHeaders
Visual Studio Code with GitHub CopilotPreregistered by MicrosoftAll optional; the agent can call list_environments and list_companies
Copilot StudioPreregistered by MicrosoftEnvironment and Company required; configuration optional
GitHub Copilot CLIYour own registrationMicrosoft’s example pins EnvironmentName; tenant and company can be omitted
Claude, ChatGPT, other MCP clientsYour own registrationDepends on the host; usually all four

In Visual Studio Code, add a businesscentral entry with the URL and "type": "http" to mcp.json, select Start, and use Copilot Chat in agent mode. In Copilot Studio, add the tool Dynamics 365 Business Central MCP Server to an agent and fill Environment, Company and, optionally, MCP Server Configuration. For other clients the transport is Streamable HTTP; HTTP/SSE is not supported. Claude Code accepts Microsoft’s documented JSON; MVP Dmitry Katson shows that Claude Desktop instead needs the mcp-remote bridge and a pinned callback port.

One detail affects many Luxembourg, French and German companies: if the company name or configuration name contains non-ASCII characters (é, ü, à), clients other than Copilot Studio must send it Base64-encoded as =?base64?<value>?=. The Advanced > Connection String action on the configuration gives you the exact header values to paste.

Authentication with Microsoft Entra ID

The server follows the MCP authorisation specification: OAuth 2.0 authorisation code flow with PKCE, Entra ID as the authorisation server, and Protected Resource Metadata so clients can discover the endpoints. There is no shared service account: operations run under the user’s identity, so audit trails show who acted.

Because Entra ID does not support Dynamic Client Registration, non-Microsoft clients need an app registration. Someone with at least the Application Developer role creates it for Multiple Entra ID tenants, adds the client’s redirect URI under Mobile and desktop applications (Claude Code uses http://localhost:<port>/callback), and adds the delegated Financials.ReadWrite.All permission for Dynamics 365 Business Central. A tenant administrator grants consent. One registration can serve several clients, and you can record its client ID for colleagues on the Model Context Protocol (MCP) Server Entra Applications page.

Security and data boundary for EU companies

A Business Central environment with an EU or EFTA localisation stores and processes its data inside the EU Data Boundary. The MCP server does not move your database. The question is what happens after a tool returns rows: they enter the context of the model behind your MCP host and are processed under that host’s terms and location—Microsoft or GitHub for Copilot Studio and GitHub Copilot, Anthropic for Claude, OpenAI for ChatGPT.

Business Central’s Allow data movement setting does not answer that question. Microsoft scopes it to Copilot and agent features that run on Business Central’s own Microsoft-managed Azure OpenAI resources. Copilot Studio has its own data residency rules and cross-region settings in the Power Platform admin center. For GDPR purposes, choosing an MCP host means choosing a processor.

  • Keep Discover Read-Only Objects off in production configurations unless you have reviewed every API the users can read, including personal data in employee and contact entities.
  • Leave Unblock Edit Tools off for pilots, and grant Allow Actions only to named objects after testing in a sandbox.
  • Separate configurations by purpose, for example read-only sales insight versus item maintenance, and let users connect with the narrowest one.
  • Treat text stored in Business Central (descriptions, comments, imported e-mail content) as untrusted input to the agent, and require human confirmation in the host before write tools run.
  • Send telemetry to Application Insights. Event RT0054 (MCP Server tool called) records the tool, configuration, client name, authenticated app ID and result of every call from version 28.0.

Licensing and cost

Microsoft’s MCP overview carries a notice that it plans to introduce charges for Business Central MCP tools, with pricing, affected tools and rollout to be announced; no price has been published. The product already signals where charges will start: in version 29.1 the Server Features list labels Data Query Tools as “Preview/Billable”. The host side already costs money: Copilot Studio requires a user licence with available Copilot Credits capacity, and third-party clients come with their own subscriptions. Each connecting person also needs a Business Central account with the relevant permissions. Budget for the host now, and expect a Business Central MCP line later.

A practical first setup checklist

  1. Start in a sandbox with representative setup and a test user that has the permission sets your future agent users will have.
  2. Assign MCP - Admin only to the people who maintain configurations.
  3. Decide the default. The built-in read-only default is a reasonable start. A configuration you mark with Set as Default applies to every client that omits ConfigurationName.
  4. Create a named configuration, activate API Tools, add only the APIs the use case needs, and keep Unblock Edit Tools off at first.
  5. Validate, fix warnings with Apply Recommended Action, then switch Active on.
  6. Connect one host. Visual Studio Code or Copilot Studio needs no app registration; for Claude or ChatGPT, register the Entra app and grant consent.
  7. Test with real questions, check answers against Business Central pages, and review RT0054 telemetry for failures.
  8. Add write access deliberately: deactivate, unblock edit tools, tick the minimum operations, validate, reactivate, then export the JSON for production.

Start with what the agent may read

Connecting an agent takes minutes. The work that protects you is choosing which host may see the data, which APIs each configuration exposes, and which users the agent can act as. If you are planning agents across finance and operations, our AI transformation service covers that design, and our Microsoft Copilot overview explains where built-in Copilot ends and custom agents begin. For the hosting side, read data sovereignty for Business Central in the EU.

SK
À propos de l'auteur
Sébastien Konsbruck
SK Consulting S.A.
LinkedIn

Want an agent on Business Central without opening the whole ledger?

We design MCP configurations, permission sets and host choices with you, test them in a sandbox, and move only what is validated to production.