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 for client_credentials | |
| BC_TENANT_ID | No | Azure AD tenant ID for client_credentials | |
| BC_URL_SERVER | No | Business Central API base URL | |
| BC_CLIENT_SECRET | No | App registration client secret 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 are clearly distinct: create, update, delete, and schema retrieval are unambiguous. However, list_items and get_items_by_field both retrieve items and could be confused, though descriptions clarify that one is general listing and the other is field-based lookup.
All tools follow a consistent verb_noun pattern: get_schema, list_items, get_items_by_field, create_item, update_item, delete_item. The mix of 'get' and 'list' for retrieval is standard and predictable.
With 6 tools covering schema access and full CRUD for items, the count is well-scoped for the server's stated purpose. No redundant tools, and each one has a clear role.
The tool surface covers the core item lifecycle (create, read, update, delete) and schema introspection. A direct get-by-ID tool is missing, but list_items with filters effectively covers that need. For a single-resource server, this is nearly complete.