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 | |
| BC_AUTH_TYPE | No | Authentication type (default: azure_cli) | 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 | |
| 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
The tools are mostly distinct, targeting schema, listing, field-based retrieval, and CRUD operations. However, list_items and get_items_by_field both retrieve items, which could cause confusion without careful reading.
Naming follows a verb_noun pattern (get_schema, list_items, create_item, update_item, delete_item). The only inconsistency is using 'list' for one retrieval and 'get' for another, but the pattern remains readable.
Six tools are appropriate for the server's purpose, providing a focused set for item management plus schema lookup without unnecessary bloat.
The toolkit covers the full lifecycle of items (create, update, delete, list, fetch by field) and includes schema access, leaving no obvious gaps for basic Business Central item operations.