Business Central MCP Server: Read-Only Analysis with Data Query Tools

Note: This blog is a personal notebook. I write it to record what I work on, for my own reference, not to publish it on social media or to promote myself. If a post is still useful to you, I am glad, but that is not why it exists.

This post was published on October 17, 2026. Software versions, product features, links, and tool availability may have changed since then. Always check official documentation for the latest information. Some screenshots show small details. Zoom in on the page to see them clearly.

Problem

A user wants to analyse customers and open sales orders without a prepared API dataset. Microsoft’s release wave 2 session shows an agent that writes AL queries for this purpose.

Why this matters

API tools work like a vending machine: the agent gets only what an administrator loaded. Data query tools work like a self-service store: the agent can read every table that the signed-in user can read. (Microsoft session) A short Available APIs list does not limit this path. Review the user’s permissions before you enable it.

Architecture

This pattern is read-only. (Microsoft configuration guidance) The external host coordinates the analysis. Business Central compiles and runs the AL queries, then returns the rows to that host. (Microsoft session)

Tool Purpose
bc_data_find_tables Find tables. (Microsoft Learn)
bc_data_get_table_schema Inspect fields. (Microsoft Learn)
bc_data_get_table_relations Find join paths. (Microsoft Learn)
bc_data_query Validate AL queries; returnData=true also executes them. (Microsoft Learn)

The agent can correct a query from the compiler errors. In the demo, a separate documentation MCP connection gives it AL guidance. Server Features are now separate from Available APIs, and System Tools shows the enabled tools. (Microsoft session)

Demo steps

I have not run this proposed test myself. Assumption: the preview is available in your Business Central online sandbox.

  1. Configure: With MCP - Admin or equivalent permissions, create an inactive configuration named SandboxOrderAnalysis. (Microsoft configuration guidance)
  2. Enable: Turn on Data Query Tools (Preview). Leave API Tools disabled and Unblock Edit Tools off. Then validate and activate the configuration. (Microsoft configuration guidance)
  3. Connect: In Copilot Studio, add the Dynamics 365 Business Central MCP Server and sign in with a limited-permission test user. Set Environment, Company, and MCP Server Configuration to the sandbox and SandboxOrderAnalysis. (Microsoft connection guidance)
  4. Ask: Use this prompt:
Analyse open sales orders for one selected customer.
Ask for an order-date range.
Inspect schemas and relations before querying.
Group quantities by item number and unit of measure.
Show the AL query, filters, and result limits.
Do not change records.

Compare the results with filtered sales orders in Business Central. Confirm that a read outside the user’s permissions fails.

The session also shows an MCP server toggle on Copilot & agent capabilities. (Microsoft session) Disable it in the sandbox, confirm that new calls fail, then enable it again.

What is intentionally simple

The test uses one customer, one company, and one date range, with no custom AL extension and no write-back.

Risks/limits

AL queries have limits on execution time and returned data. (Microsoft session) Check the agent’s joins and filters, and review how the host handles returned data.

Data Query Tools are still in preview. Microsoft plans charges for MCP tools, but the cited guidance has no pricing or rollout details. (Microsoft configuration guidance; Microsoft MCP overview) Check the current terms before production use.

Next iteration

Keep the expected totals as a test case. Repeat the permission checks before you expand access.

Closing note

I would use this path for exploration. For repeated reporting, I would prefer a reviewed dataset with an agreed definition.

← Back to BC MCP