Business Central MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BC_PASS | Yes | Your Business Central API password | |
| BC_USER | Yes | Your Business Central API username | |
| BC_COMPANY | Yes | The name of your Business Central company | |
| BC_URL_SERVER | Yes | Your Business Central API server URL (e.g., 'https://api.businesscentral.dynamics.com/v2.0/tenant/api/v2.0') |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| BC_Get_SchemaC | Get schema information for a Business Central resource. |
| BC_List_ItemsC | Get items from Business Central with filtering and pagination. |
| BC_Get_Items_By_FieldC | Get items matching a field value. |
| BC_Create_ItemC | Create a new item in Business Central. |
| BC_Update_ItemC | Update an existing item in Business Central. |
| BC_Delete_ItemC | 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 targets a distinct action on items (create, delete, get by field, get schema, list, update), with no overlap in purpose.
All tools use a consistent BC_verb_noun pattern in snake_case, though mixing 'Get' and 'List' for item retrieval is a minor inconsistency.
Six tools cover the essential CRUD operations plus schema and filtered lookup, which is well-scoped for an item management server.
Basic CRUD is covered, but there is no explicit get-by-id tool (though BC_Get_Items_By_Field could serve that purpose), leaving a minor gap.