Plur-e MCP · Model Context Protocol
Talk to Business Central and Dynamics 365 CRM — through Claude
Plur-e MCP servers expose your ERP and CRM as governed tools for Claude, by Anthropic, and other MCP clients: real data, real actions, your users' permissions, full audit.
- Example prompts
- “What's on hand for item 1896-S across all locations?”
- “Create a sales quote for Conchita Foods with 40 cases of SKU 20112 at list price.”
- “Which purchase orders are late this week, and who is the vendor contact?”
- “Summarize the last five cases for account Adventure Sports and draft a follow-up.”
Quick answer
Plur-e MCP is a set of Model Context Protocol (MCP) servers for Microsoft Dynamics 365 Business Central and Dynamics 365 CRM (Dataverse). They let Claude, by Anthropic — in Claude.ai, Claude Desktop, Claude Code or custom agents built on the Claude API — read and, when allowed, write ERP and CRM data through tools with per-user authentication, scopes, approvals and logging. Plur-e designs, deploys and operates them for customers, in Plur-e's cloud or in the customer's Azure tenant.
How it works
A Claude client connects
Claude.ai connectors, Claude Desktop, Claude Code or your own agent built on the Claude API or Agent SDK.
Plur-e MCP exposes governed tools
Each tool has a name, a schema and a scope. Read tools are on by default; write tools are enabled per role and can require approval.
Calls run as the user
Authentication is per user with Microsoft Entra ID (OAuth). Claude never sees more than the user's Business Central or Dataverse permissions allow.
Everything is logged
Every request, tool call and result is recorded. Writes carry the approving user, the payload and the resulting document number.
Tools
MCP for Business Central
Customers, items, availability, sales, purchasing, warehouse, posted documents.
ToolsMCP for Dynamics 365 CRM
Leads, accounts, contacts, opportunities, quotes, cases, activities.
ToolsPlur-e Docs MCP
Public, read-only server over this documentation. Add Plur-e docs to Claude.
ToolsGovernance first
| Identity | Per-user OAuth with Microsoft Entra ID; no shared service account for user-facing tools |
|---|---|
| Default posture | Read-only. Write tools are opt-in per role and can require human approval |
| Scopes | Tools grouped by area (sales, purchasing, inventory, warehouse, CRM) and enabled per customer and role |
| Audit | Full request and tool-call log with user, timestamp, inputs and outputs |
| Rate limits | Per user and per tenant, configurable |
| Data | No training on your data. Prompts and results are processed by the Claude API under Anthropic's commercial terms. VALIDAR: data retention setting |
| Hosting | Plur-e cloud (Azure) or your Azure tenant |
Why Plur-e for MCP
- We already run Business Central integrations in production: Plur-e Mobile posts warehouse, sales and payment documents every day.
- We know the Business Central and Dataverse APIs, permissions and posting rules — the parts that make an agent safe, not just impressive.
- We build in .NET and TypeScript and ship MCP servers with tests, logs and versioned tool schemas.
- We have shipped custom MCP tools for customers. VALIDAR: publishable case.
- We have operated an AI assistant inside Business Central since 2024 (the Chat Bot Assistant). VALIDAR date.
Looking for the assistant inside Business Central? That is the Chat Bot Assistant (OpenAI). AI Assistant
How an engagement runs
How an engagement runs
Discovery workshop (2 h)
Map the questions your teams ask every day, the data behind them and who may act on what.
Pilot (2–4 weeks)
Three to five tools for one team, connected to a sandbox or production with read-only scopes. Real users, real prompts.
Production
Governance (roles, approvals, logs), monitoring, training and documentation. Optional write tools.
Managed service
We operate the servers, ship new tools as your processes change and keep up with Business Central releases.
Priced per project. DECISIÓN: publish workshop and pilot prices.
FAQ
Frequently asked questions
Start with a two-hour discovery workshop
Bring the questions your team asks every day. We map them to tools, permissions and a pilot plan.