Skip to main content
Glama
d365-dmf-mcp

d365-dmf-mcp

by ahaugerud

d365-dmf-mcp

MCP server that imports CSV files into Dynamics 365 F&O via Data Management (DMF). It runs locally and authenticates as the user signed in to the Azure CLI.

Setup on Windows

  1. Install uv and the Azure CLI.

    winget install astral-sh.uv Microsoft.AzureCLI
  2. Sign in with the account that has access to D365 (if there is no az session, the server falls back to an interactive browser login):

    az login --tenant <entra-tenant-id>
  3. Register the server with Claude Code (runs the published package via uvx; see .mcp.json.example):

    claude mcp add d365-dmf `
      -e DMF_AZURE_TENANT_ID=<entra-tenant-id> `
      -e DMF_BASE_URL=https://<env>.sandbox.operations.eu.dynamics.com `
      -- uvx d365-dmf-mcp

    Other MCP clients: copy the block from .mcp.json.example into the client's MCP config. To run from a local checkout instead, use uvx --from C:\path\to\d365-dmf-mcp d365-dmf-mcp.

Related MCP server: D365 Finance & Operations MCP Server

Tools

Only the tenant and environment URL are config. Everything else is passed per call.

  • import_data(definition_group, company, files, format="CSV"): import one or more files into a data project and wait for the result. files is a list of {entity, file_path}; entity is the DMF entity name as shown in D365 (e.g. Customer groups) and the file (.csv or .xlsx) has the entity's field names (e.g. CUSTOMERGROUPID) in its first row. The server generates the package manifest, looks up each entity's target and the dependency order from D365, and creates the data project if it doesn't exist. format is free text (CSV, EXCEL, or any CSV/Excel-based D365 source format on the environment, e.g. CSV-Unicode).

  • export_data(output_dir, definition_group, company): run an existing export data project and save its files.

  • create_data_project(name, description=""): create an empty import data project (optional; import_data does this itself).

  • list_data_projects(name_filter="", operation_type=""): browse existing data projects.

  • list_project_entities(definition_group): the entities in a project, with format, execution order and any non-default processing settings.

  • configure_project_entity(definition_group, entity, ...): show/change per-entity settings (business validation, field validation, business logic, skip staging, fail-on-error). Defaults are right for almost all imports; only relax validation for large, already-tested migration loads.

  • search_entities(query, limit=50): search the DMF entity catalogue by name, target entity or module.

  • get_entity_fields(entity): the column names (data file header), types, lengths and required flags for an entity.

  • get_execution_status(execution_id): check the status of an execution, with errors if it failed.

Notes

  • Import threshold record count, import task count (parallelism), set-based processing and change tracking have no API; set them in D365 (Data management > Framework parameters > Entity settings > Configure entity execution parameters) for large loads.

  • Composite and XML-based entities are not supported.

  • Optional env vars: DMF_POLL_INTERVAL_SECONDS (default 5), DMF_POLL_TIMEOUT_SECONDS (default 300).

Available Tools

8 tools
create_data_projectB

Create an empty DMF import data project. Optional: import_data creates the project itself if it doesn't exist, and the first import defines its entities.

Inputs: name (required), description. Returns: result

export_dataB

Run an existing DMF export data project and save its data files to output_dir.

The files are saved in the project's own source format (CSV, Excel, ...). Returns the saved paths.

Inputs: company (required), output_dir (required), definition_group (required). Returns: result

get_entity_fieldsA

List the importable columns of a DMF entity: the staging column names to use as the header row of the data file, with data type, max length and whether D365 flags the field as required. System-managed fields are omitted.

Inputs: entity (required). Returns: result

get_execution_statusB

Get the status of a DMF execution (NotRun, Executing, Succeeded, PartiallySucceeded, Failed, Canceled), with per-entity status and error messages if it failed.

Inputs: execution_id (required). Returns: result

import_dataA

Import one or more data files into D365 through a DMF data project, as the signed-in user.

definition_group is the data project name (created automatically if it doesn't exist), company the legal entity id (e.g. USMF). files lists {entity, file_path} pairs: entity is the DMF entity name as shown in D365 (e.g. "Customer groups"; find it with search_entities), file_path a .csv or .xlsx whose first row holds the entity's field names (staging column names, e.g. CUSTOMERGROUPID; list them with get_entity_fields). Several entities can be imported in one call; D365 decides the order from their dependencies. format is the file format in the package, free text and case-insensitive: "CSV" (default) and "EXCEL" are the common ones; other CSV/Excel-based source formats on the environment (e.g. "CSV-Unicode") also work. An unknown value returns the available ones. Composite and XML-based entities are not supported. With wait=True, polls until the import finishes (or the timeout); otherwise returns the execution id to check with get_execution_status. dry_run only validates and builds the package.

Inputs: files (required), company (required), definition_group (required), wait, +2 more. Returns: result

list_data_projectsA

List existing DMF data projects (name, Import/Export, description).

name_filter is a case-insensitive substring of the name or description; operation_type optionally restricts to "Import" or "Export". Use the names with import_data / export_data.

Inputs: name_filter, operation_type. Returns: result

list_project_entitiesB

List the entities defined in a DMF data project, with source format and execution order (unit/level/sequence).

Inputs: definition_group (required). Returns: result

search_entitiesA

Search the DMF entity catalogue by case-insensitive substring of the entity name, target entity or module (e.g. "customer", "AccountsReceivable"). Returns entity names to use with import_data, plus category and module. Composite entities (X composite) are not importable here.

Inputs: query (required), limit. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct DMF operation: entity catalogue search, field metadata, import, export, project listing/creation, project entity listing, and execution status. The only redundancy is that import_data can auto-create a data project, but create_data_project remains clearly scoped as an optional explicit step.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case convention (get_execution_status, search_entities, import_data, etc.). There are no mixed styles or vague names.

    Tool Count5/5

    Eight tools are well-scoped for a DMF import/export server. Each tool has a clear role, and the surface is neither too thin nor bloated.

    Completeness4/5

    The core import workflow is complete end-to-end: search entities, inspect fields, import data, and check execution status. Minor gaps remain: no tool to create/configure export projects, cancel running executions, or delete/update data projects, though some can be worked around via existing projects or wait/timeout behavior.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables comprehensive management of Microsoft Dataverse environments, including schema operations for tables, columns, and relationships through the Dataverse Web API. It also supports solution management, security role configuration, and the generation of WebAPI calls and Mermaid ERD diagrams.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to explore metadata, query data, and perform write operations across multiple Microsoft Dynamics 365 Finance & Operations environments. It features specialized tools for OData execution and data analysis with built-in read-only safety for production environments.
      38 npm
      10
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to search and analyze Microsoft Dynamics 365 Finance & Operations artifacts, read local source code, and generate context-aware solutions through natural language.
      71 npm
      12
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language interaction with Microsoft Dynamics 365 Finance & Operations, including entity discovery, CRUD operations, and a learning system that improves over time.
      MIT