mcp-dynamics-365
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| D365_BASE_URL | Yes | Your Dynamics 365 organization URL | |
| D365_RESOURCE | Yes | Resource URL for Dynamics 365 API (usually the same as D365_BASE_URL) | |
| D365_CLIENT_ID | Yes | Azure AD application client ID | |
| D365_TENANT_ID | Yes | Azure AD tenant ID | |
| D365_CLIENT_SECRET | Yes | Azure AD application client secret |
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_entity_schemaC | Get detailed schema information for a specific Dynamics 365 entity |
| get_attribute_schemaB | Get detailed schema/metadata for a specific attribute of a Dynamics 365 entity, including options for picklists |
| list_entitiesB | List all available Dynamics 365 entities with their basic information |
| query_entitiesC | Query entities from Dynamics 365 with optional filtering, sorting, and pagination |
| get_entityB | Get a specific entity record by ID from Dynamics 365 |
| create_entityC | Create a new entity record in Dynamics 365 |
| update_entityC | Update an existing entity record in Dynamics 365 |
| delete_entityC | Delete an entity record from Dynamics 365 |
| execute_odata_queryB | Execute a custom OData query against Dynamics 365 Web API |
| execute_functionC | Execute a custom Dynamics 365 function or action |
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 10 tools
Most tools have distinct purposes (e.g., create/update/delete and execute_odata_query vs query_entities). However, query_entities and execute_odata_query could be confused by an agent when deciding between structured querying and raw OData. Also get_entity_schema and get_attribute_schema are clearly different, but get_entity and get_entity_schema share the 'get_entity' prefix, potentially causing slight naming ambiguity.
All tool names follow a consistent snake_case verb_noun pattern (e.g., get_entity_schema, list_entities, create_entity). The verbs are standard and the naming is predictable throughout.
10 tools is well-scoped for a Dynamics 365 API wrapper, covering essential CRUD, metadata, and query operations without being excessive. Each tool has a clear, non-redundant role.
The surface provides comprehensive CRUD and query capabilities, including schema introspection and custom function execution. However, it lacks tools for bulk operations, association management (e.g., associate/disassociate records), and batch requests, which are common in Dynamics 365.