Microsoft Business Central MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BC_COMPANY | No | Company display name in Business Central | |
| BC_AUTH_TYPE | No | Authentication type: 'azure_cli' (default) or 'client_credentials' | azure_cli |
| BC_CLIENT_ID | No | App registration client ID (required for client_credentials) | |
| BC_TENANT_ID | No | Azure AD tenant ID (required for client_credentials) | |
| BC_URL_SERVER | No | Business Central API base URL (e.g., https://api.businesscentral.dynamics.com/v2.0/{tenant}/Production/api/v2.0) | |
| BC_CLIENT_SECRET | No | App registration client secret (required for client_credentials) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_schemaB | Get schema information for a Business Central resource |
| list_itemsA | Get items from Business Central with filtering and pagination |
| get_items_by_fieldB | Get items matching a field value |
| create_itemC | Create a new item in Business Central |
| update_itemC | Update an existing item in Business Central |
| delete_itemB | Delete an item from Business Central |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Most tools have clearly distinct purposes, but list_items and get_items_by_field both retrieve items and could be confused. The descriptions differentiate them (broad listing vs. field-specific lookup), so the overlap is minor.
All tool names follow a consistent snake_case verb_noun pattern (get_schema, list_items, create_item, etc.). This makes the tool set predictable and easy to navigate.
With 6 tools, the set is well-scoped for item management plus schema access. Each tool serves a distinct function without redundancy or excessive bloat.
The set provides full CRUD coverage for items (create, read/update/delete) and adds schema inspection. Missing a direct get_item by ID, but list_items with filtering likely covers that use case. The scope is item-focused rather than covering all Business Central resources, but that seems intentional.