MCP tool calls fail with Internal_CompanyNotFound

(0) Share

Report

Posted on by CU17081145-2

Since the MCP 2026-07-28 stateless spec rollout, we're seeing all data-returning tool calls against the Business
Central MCP server (https://mcp.businesscentral.dynamics.com) fail with Internal_CompanyNotFound. Metadata calls
(search/describe actions) still work fine — only calls that actually need company/tenant/environment context fail.

We're hitting this from two independent integration paths:
- A custom MCP proxy in front of BC, used from Claude
- Microsoft Copilot Studio

Since both clients fail the same way, this looks like it's on the BC MCP server side — most likely related to
company/tenant context (TenantId, EnvironmentName, Company) no longer being reliably resolved per-request now that the
MCP spec is stateless (previously this context was bound once per session).

Questions for the community:
1. Is this a known issue on Microsoft's side, and is a fix planned for the next Business Central release (28.5)?
2. Has anyone found a reliable workaround in the meantime?

Any input appreciated — this is currently blocking BC MCP usage for us regardless of client.

I have the same question (0)

All responses (1)

Answers (0)

ParthPatel249 80 on at

Like (0)

Report
Copy link

Link copied!
The 2026-07-28 stateless MCP spec broke per-request company context resolution. TenantId, EnvironmentName, and Company were previously session-bound, now the BC MCP server fails to resolve them per-request, causing Internal_CompanyNotFound on all data calls. Metadata calls don't need company context, which is why those still work.
Workarounds
1. Pass context explicitly in every tool call
{ "company": "Your Company Name", "environment": "Production", "tenantId": "your-tenant-id" }
2. Inject headers in your MCP proxy
BCEnvironment: Production BCCompany: YourCompanyName
3. Copilot Studio, temporarily replace the MCP action with the native Business Central connector for data-returning calls.
On the Fix
This isn't publicly confirmed yet for BC 28.5. Raise a support ticket referencing the 2026-07-28 stateless rollout and Internal_CompanyNotFound, and track github.com/microsoft/BCTech for any updates from the BC engineering team.

Was this reply helpful? Yes No