VANGELDER SOLUTIONS MCP Guard · Help NederlandsFrançais Product

docs.vangeldersolutions.be/mcp-guard/troubleshoot-connection

Troubleshoot the BC MCP Pro Connector

This article covers the messages that the BC MCP Pro connector shows when it reads the user's rule from the MCP Guard extension in Microsoft Dynamics 365 Business Central and cannot continue. The messages come from the connector, so the user sees them in the AI assistant and not in Business Central. In some messages the connector still calls the extension BC MCP Pro. Each heading is the start of the message. The words in italics stand for a value that differs per case.

BC MCP Pro (MCP Guard) is not installed in environment name, or its version is too old

Cause: The extension is missing in the environment the connector chose, or the versions of the extension and the connector do not match. An old connector can also show this message for a newer version of the extension.

Solution:

  1. Install or update the extension in that environment from Microsoft Marketplace. See Install the MCP Guard Extension.
  2. Update the connector to its latest version.

Whether MCP Guard is installed could not be checked in name

Cause: Business Central did not answer in that environment, so the connector cannot tell whether the extension applies.

Solution: Try again shortly. The message clears on its own.

No BC MCP Pro licence is assigned to user

The full message continues:

Ask your administrator to assign one in the Microsoft 365 admin center (Billing > Licenses)

Cause: Business Central refused to return the user's rule, because no MCP Guard licence is assigned to the user. In a sandbox environment this message also appears for a user without a licence when no rule applies to them.

Solution: Assign an MCP Guard licence to the user in the Microsoft 365 admin center. See Assign Licences.

The connection is refused because the permission set MCP GUARD - USER is missing

Cause: The connector refuses the connection because the user has no permission set that includes MCP GUARD - USER, so the user cannot read their rule. On the MCP Guard User Settings page, the User Permission Set column shows Not found for that user.

Solution: Assign MCP GUARD - USER to the user. See Permission Sets.

MCP Guard allows user to use companies in environment name, but the account has no permissions in any of those companies

Cause: The companies in the Allowed Companies field of the user's rule and the companies in which the user has Business Central permissions do not overlap.

Solution: Change one of the two.

  1. On the MCP Guard User Settings page, add a company the user has permissions in to Allowed Companies, or
  2. Give the user permission sets in one of the allowed companies in Business Central.

See Environments and Companies.

Company name is not available for this connection

Cause: The AI assistant asked for a company that is not in the allowed companies of the user's rule. This is the rule doing its work.

Solution: None, when the company should stay out of reach. When the user should be able to use the company, add it to Allowed Companies on the user's rule.

Business Central rejected the connection (HTTP 400/404)

Cause: The MCP configuration that the user's rule names does not exist in the environment, or it is not active.

Solution:

  1. Open the MCP Server Configurations page in the environment.
  2. Check that the configuration with the name from the MCP Configuration field of the rule exists.
  3. Check that Active is switched on for that configuration.

See MCP Configurations.

A sandbox environment is missing in the AI assistant

Cause: The connector leaves out an environment where the extension does not admit the user. For a sandbox environment, that happens when:

  • The user switched the AI assistant off for themselves on the My MCP Guard page in that sandbox.
  • The user has no MCP Guard licence and no rule applies to the user there.

Solution:

  1. When the user switched it off, the user opens My MCP Guard in that sandbox and turns AI Assistant in This Sandbox on. The sandbox is back within ten minutes. See Switch the AI Assistant On or Off in a Sandbox.
  2. Otherwise, add a rule for the user in that sandbox, or assign a licence. See Assign Licences.

A rule was changed, and the AI assistant still uses the old companies or configuration

Cause: The connector reads the rule when it starts. It keeps the result on the user's device so that the next start is fast, and checks the rule again in the background.

Solution: Start the connector again. A changed rule, a removed licence or removed access is shown at a following start.

Where to find the log

When the connector runs as an extension in Claude Desktop, the log is the file mcp-server-BC MCP Pro.log in the log folder of Claude Desktop:

  • Windows: %LOCALAPPDATA%\Claude\Logs
  • macOS: ~/Library/Logs/Claude