Connect with the BC MCP Pro Connector
The BC MCP Pro connector of Vangelder Solutions links an AI assistant to Microsoft Dynamics 365 Business Central. When it starts, it reads the rule of the signed-in user from the MCP Guard extension and applies it: the allowed companies, the default company, the MCP configuration, the access levels and the daily limits. The connector can also report the usage of each user. Every call still runs under the user's own Business Central account, so permission sets and security filters apply unchanged.
Before you start
In each environment users work in:
- The MCP Guard extension is installed. See Install the MCP Guard Extension.
- Each user has an MCP Guard licence and the permission set MCP GUARD - USER. See Assign Licences.
- The MCP configurations that the rules name exist and are Active. See MCP Configurations.
Use the latest version of the connector, and update the connector before you update the extension. Some parts of a rule need a minimum version of the connector. An older connector ignores them.
| Part of the rule | Needs |
|---|---|
| General Access | Connector 0.8.0 or later, or the cloud edition 0.11.0 or later. See General Access. |
| Usage reporting | The cloud edition 0.12.0 or later, with reporting switched on. See Usage per User. |
| Daily Call Limit and Daily Change Limit | The cloud edition 0.13.0 or later, with usage reporting switched on. The desktop connector does not apply them. See Daily Limits. |
What the connector does when it starts
- Sign-in. The user signs in with Microsoft once.
- Environment. The connector uses the environment that is filled in. Otherwise it takes production environments first, then the others alphabetically, and picks the first one where the user has permissions in at least one company.
- Companies. For each company, the connector checks whether the user may work there.
- Rule. The connector reads the rule of the user from the
mcpUserSettingsAPI page. This call is also the licence check. - Connection. The connector connects to the MCP server of Business Central with the resulting company and MCP configuration, with company switching limited to the allowed companies, and with the tools the user may not use hidden.
What the connector reads from the extension
The page MCP Guard User Settings API (73633179) returns at most one row: the rule that applies to the signed-in user.
GET https://api.businesscentral.dynamics.com/v2.0/{tenantId}/{environment}/api/vangelderSolutions/mcpguard/v1.0/companies({companyId})/mcpUserSettings
| Field | Meaning |
|---|---|
allowedCompanies | Company names, separated by semicolons. Empty means every company the user has permissions in. |
defaultCompany | The company the connection opens in. When it is not in the allowed set, the first allowed company is used. |
configurationName | The name of the MCP configuration. Empty means the default configuration of the environment. |
settingSource | User or Group: where the rule comes from. |
licenceSource | Licensed, or SandboxRule for a user without a licence in a sandbox environment. |
productionAccess, planningAccess, assemblyAccess, projectAccess | The access level per module. |
generalAccess | The access level for everything outside the extension's own API pages. |
dailyCallLimit, dailyChangeLimit | The daily limits. 0 means no limit. |
No row means that no rule applies: the user gets every company they have permissions in and the default MCP configuration.
In a sandbox environment, a user who switched the AI assistant off on the My MCP Guard page gets an answer as if no rule applies, and the connector leaves that sandbox out. See Switch the AI Assistant On or Off in a Sandbox.
Several environments
The BC MCP Pro connector can keep every environment where the user has permissions and where the extension admits the user. It then reads the rule once per environment. An environment without the extension, or where the user has no licence, is skipped. The user only sees a message when no environment is left.
Rules are per environment. Install the extension and make the rules in each environment users should reach.
Access levels in the connector
The connector reads the access levels and hides what the rule does not allow: a tool or action of the extension's API pages that needs a higher level is left out of the tool list. Business Central enforces the same levels on the server, so the result is the same when a user connects with another MCP client. See Access Levels per Module.
For General Access, the connector is the only enforcer. It hides and refuses the actions on Business Central's standard pages that are above the level. See General Access.
What the connector applies, and what Business Central enforces
The companies, the default company, the MCP configuration, General Access, the daily limits, the usage reporting and the sandbox switch are applied by the connector. They are a policy, not a security boundary: a user who uses another MCP client can still choose another company or configuration, and is not limited by them. The access levels per module and all permissions are enforced by Business Central.