Microsoft Business Central MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BC_COMPANY | Yes | Company display name, e.g., 'My Company' | |
| BC_AUTH_TYPE | No | Authentication type. Default is 'azure_cli'. Use 'client_credentials' for service-to-service authentication. | azure_cli |
| BC_CLIENT_ID | No | App registration client ID. Required when BC_AUTH_TYPE is 'client_credentials'. | |
| BC_TENANT_ID | No | Azure AD tenant ID. Required when BC_AUTH_TYPE is 'client_credentials'. | |
| BC_URL_SERVER | Yes | Business Central API base URL, e.g., https://api.businesscentral.dynamics.com/v2.0/{tenant-id}/Production/api/v2.0 | |
| BC_CLIENT_SECRET | No | App registration client secret. Required when BC_AUTH_TYPE is '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
Each tool has a clear distinct purpose: schema retrieval, listing with filtering, field-based search, and standard CRUD operations. No overlap exists.
All tools follow a consistent verb_noun pattern in snake_case (e.g., get_schema, create_item), making naming predictable and clear.
With 6 tools covering schema retrieval and full CRUD for items, the set is well-scoped and each tool serves a necessary function.
Covers all essential operations for items: create, read (list and field-based), update, delete, plus schema metadata. No obvious gaps for the item-focused domain.