Connect your AI client

Quick answer

Plur-e MCP servers are remote MCP servers (Streamable HTTP) with their own OAuth 2.1 authorization server: add the server URL in your client, press Connect and sign in with your Microsoft work account. There is no client id or secret to configure — the server registers your client automatically and, if your account is registered in Plur-e, connects it to your tenant.

Before connecting

1. Plur-e activates the AI & MCP module on the tenant's subscription.
2. A tenant administrator opens AI & MCP → Settings in the Admin Center to pick the Business Central environment and company and enable the server, then AI & MCP → Roles to grant entities/areas and actions to users — or rely on the Default access role Plur-e creates automatically for read-only access.
3. Each user must exist in the Admin Center (Security → Account Users) with the same Microsoft account they use to sign in; the server rejects unknown accounts.

Administrators see and revoke connected clients in AI & MCP → AI connections in the Admin Center; a revoked connection stops working immediately and the user must connect again.

Troubleshooting

• "This Microsoft account is not registered in Plur-e. Ask your administrator to invite you." The signed-in account has no matching user in the tenant. Ask a tenant administrator to invite you in the Admin Center (Security → Account Users) with the same Microsoft account, then connect again.
• The connector connects but every tool call fails or is empty. The tenant likely has not enabled the AI & MCP module, or an administrator has not configured the environment yet or assigned any MCP role — see the requirements above.
• You are Plur-e staff or a partner and need a different tenant. Your account is not tied to one tenant. The consent screen you saw when connecting let you fix this connection to a tenant (a dropdown listing the tenants you can act on, plus "No fixed tenant" for a connection you switch per session); if you picked a tenant there, every tool call already uses it. Either way, select_tenant still works on both the /bc and /crm servers to switch tenant for the rest of the session — ask your AI assistant to call it (or send it as the very first request).
• Your client cannot open a browser (headless agent, CI). The Connect flow needs an interactive sign-in. Existing integrations that already obtain a Microsoft Entra ID access token directly can keep passing it as a bearer header instead (an Authorization: Bearer <token> header, or the equivalent option in your MCP client); new setups should use the interactive flow above.

Related: MCP security model · MCP roles