Devart MCP Server for Dynamics 365 (ADO.NET)

com.devartPublished by devart.comv1.1.0Updated Oct 24, 2026

Schema-aware read/write access to Dynamics 365 through Devart dotConnect ADO.NET data provider.

VerifiedSTDIODesktop onlyDatabasesData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

A local MCP server that gives an AI assistant schema-aware read/write access to Dynamics 365 business data through Devart dotConnect ADO.NET or ODBC drivers.

What you can do
Query Dynamics 365 data in natural language, translated into structured queries and executed through Devart connectivity drivers, with structured results returned to the assistant. Read and write Dynamics 365 records through a schema-aware connection. Support analysis and reporting on sales pipeline, accounts and contacts, service cases, marketing campaigns, activity history, and revenue or quota data. Run over stdio, started automatically by the AI client, or over HTTP on a configured port.
When to use it
Useful for teams whose primary business data lives in Dynamics 365 and who want to query, analyze, or update it conversationally instead of exporting or writing manual queries. Fits sales, customer service, marketing, and revenue reporting workflows.
Requirements
Runs as a local Windows process (desktop only). Needs .NET 8 SDK to build from source, a Devart dotConnect for Dynamics 365 or Devart ODBC Driver for Dynamics 365 connection, and a connection configured in an mcpserver.json file next to the executable. The connection string is supplied through the DEVART_MCP_DYNAMICS365_CONNECTION environment variable.
Before you install
The server provides read/write access to Dynamics 365, so assistant actions can change business records. The connection string, which may include credentials and a license key, is held in a secret environment variable and a local configuration file. The required Devart ODBC Driver is a paid product with only a 30-day trial. Review what data leaves your environment before use.

Installation

In SourceWeft

  1. Open Devart MCP Server for Dynamics 365 (ADO.NET) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[Devart MCP Server for Dynamics 365]

Version 1.1.0

What's new · Changelog

Devart MCP Server for Dynamics 365

Devart MCP Server for Dynamics 365 enables AI clients to interact with your data through a secure server running in your environment. It turns a regular AI chat into a practical way to work with real-world business data — and it is faster than conventional export or manual querying.

Key benefits

Devart MCP Server for Dynamics 365 allows you to:

  • Work with data intuitively through natural language.
  • Retrieve the required data for analysis within minutes.
  • Report on your data faster with AI-powered assistance.
  • Minimize manual data handling and integration maintenance.

How it works

Devart MCP Server for Dynamics 365 helps AI clients communicate directly with Dynamics 365 databases using natural-language prompts. It translates AI requests into structured queries, executes them through Devart connectivity drivers, and returns clean, structured results for seamless AI-powered data access.

[Devart MCP Server architecture]

Quick start

To get started with Devart MCP Server for Dynamics 365:

1. Download and install Devart ODBC Driver for Dynamics 365.

2. Download and install Devart MCP Server for Dynamics 365.

3. In Devart MCP Server for Dynamics 365, configure your data connection and integration settings.

[Devart MCP Server configuration]

4. Run your first natural-language query.

[Need an MCP Server for multiple data sources?]

Manual installation and configuration

Prerequisites

Before building and running Devart MCP Server for Dynamics 365, ensure the following components are installed:

  • .NET 8 SDK
  • ADO.NET connection — Devart.AI.McpServer.AdoNet.Dynamics365.csproj Devart dotConnect for Dynamics 365 (installed automatically via NuGet during build)
  • ODBC connection — Devart.AI.McpServer.Odbc.Dynamics365.csproj Devart ODBC Driver for Dynamics 365 (requires manual download and installation)

Step 1: Clone the repository

Clone the project repository and navigate to the project directory:

1. Open Command Prompt.

2. Enter the following command:

cmd
git clone https://github.com/devart-ai-connectivity/devart-mcp-server-dynamics365.gitcd devart-mcp-server-dynamics365

Step 2: Build the MCP Server from source

You can build Devart MCP Server for Dynamics 365 from source using either of the supported database connectivity technologies: ADO.NET or ODBC.

  • To build the MCP server with ADO.NET, run the following command:
cmd
dotnet publish Devart.AI.McpServer.AdoNet/Devart.AI.McpServer.AdoNet.Dynamics365/Devart.AI.McpServer.AdoNet.Dynamics365.csproj -c ReleaseDynamics365 /p:TargetFramework=net8.0

The Devart dotConnect for Dynamics 365 NuGet package is downloaded and restored automatically.

  • To build the MCP server with ODBC, select the command based on the bitness of your data source.

For 64-bit data source, run the following command:

cmd
dotnet publish Devart.AI.McpServer.Odbc/Devart.AI.McpServer.Odbc.Dynamics365/Devart.AI.McpServer.Odbc.Dynamics365.csproj -c ReleaseDynamics365 -r "win-x64" /p:TargetFramework=net8.0

For 32-bit data source, run the following command:

cmd
dotnet publish Devart.AI.McpServer.Odbc/Devart.AI.McpServer.Odbc.Dynamics365/Devart.AI.McpServer.Odbc.Dynamics365.csproj -c ReleaseDynamics365 -r "win-x86" /p:TargetFramework=net8.0

Note

The target platform must match the bitness of your ODBC data source.

Step 3: Configure the database connection for the MCP Server

1. Create an mcpserver.json configuration file in the directory containing the built MCP Server executable.

2. In the file, configure the database connection.

  • Configure a connection with ADO.NET.

Add the following configuration to the mcpserver.json file:

json
{  "Connections": [    {      "Name": "my_dynamics365",      "ConnectionString": "Authentication Type=RefreshTokenInteractive;Server=your_host;License Key=your_license_key;",      "ProtocolType": "stdio"    }  ]}
  • Configure a connection with ODBC.

Add the following configuration to the mcpserver.json file:

json
{  "Connections": [    {      "Name": "my_dynamics365",      "DsnName": "your_dsn_name",      "ProtocolType": "stdio"    }  ]}
  • Configure a connection with ODBC using a connection string.

Add the following configuration to the mcpserver.json file:

json
{  "Connections": [    {      "Name": "my_dynamics365",      "ConnectionString": "Driver={Devart ODBC Driver for Dynamics 365};Server=localhost;User ID=dynamics;Password=your_password;Database=your_database;",      "ProtocolType": "stdio"    }  ]}

where:

  • Name — The connection name.

  • ConnectionString (applies to ADO.NET) — A database-specific connection string used to establish a connection to the target database.

  • DsnName (applies to ODBC) — The name of your data source.

  • ProtocolType — A transport protocol. The possible options are: stdio or http.

  • HttpPort (required if ProtocolType is set to http) — The port number for the http protocol.

Step 4: Run the MCP server

After you configure the MCP Server, you can start it.

Note

This step is required only when ProtocolType is configured as http. If you use the stdio transport protocol, your AI client starts the server automatically.

  • To start the server with ADO.NET, run the following command:
cmd
Devart.AI.McpServer.AdoNet.Dynamics365.exe run my_dynamics365
  • To start the server with ODBC, run the following command:
cmd
Devart.AI.McpServer.Odbc.Dynamics365.exe run my_dynamics365

where my_dynamics365 is the name of the ODBC connection.

Step 5: Integrate with Claude Desktop

1. Open claude_desktop_config.json, the Claude configuration file.

Tip

If you can't locate the configuration file, it may not exist yet. To create it, open Claude Desktop and navigate to File > Settings > Developer, then click Edit Config. The folder with the claude_desktop_config.json file opens.

2. Add one of the following objects, depending on the transport protocol used by MCP Server:

  • STDIO
json
{  "mcpServers": {    "devart": {      "command": "C:\\path\\to\\Devart.AI.McpServer.AdoNet.Dynamics365.exe",      "args": [        "run",        "my_dynamics365"      ]    }  }}

where:

  • devart is the connector name that will appear in Claude Desktop.

  • C:\\path\\to\\Devart.AI.McpServer.AdoNet.Dynamics365.exe is the path to the executable file. For an ODBC connection, use Devart.AI.McpServer.Odbc.Dynamics365.exe.

  • my_dynamics365 is the connection name specified in the mcpserver.json configuration file.

  • HTTP

    json
      "mcpServers": {    "devart": {      "command": "npx",      "args": [        "-y",        "mcp-remote",        "http://localhost:5000/sse"      ]    }  }

    where:

    • devart is the connector name that will appear in Claude Desktop.
    • 5000 is the MCP Server listening port.

3. Save the file.

4. Restart Claude Desktop.

Devart MCP Server for Dynamics 365 is now integrated with Claude, and devart appears in the Claude Desktop app in Customize > Connectors.

You can also integrate Devart MCP Server for Dynamics 365 with other AI clients such as Cline, Codex, Cursor, Visual Studio Code, Windsurf, Zed.

Supported clients

Devart MCP Server for Dynamics 365 supports integration with the following AI clients:

  • Claude Desktop
  • Visual Studio Code
  • Cursor
  • Codex
  • Windsurf
  • Cline
  • Zed
  • ...and other MCP-compatible AI clients

Typical use cases

Devart MCP Server for Dynamics 365 is a practical fit for teams working with Dynamics 365 as their primary data source.

  • Sales pipeline analysis and forecasting
    Let sales managers and reps query opportunity stages, deal values, close probabilities, and pipeline health directly from Dynamics 365 in natural language.

  • Customer and account intelligence
    Access full account histories, contact interactions, and relationship timelines stored in Dynamics 365 to support account management and customer research.

  • Service queue and case management analytics
    Analyze open cases, resolution times, agent workloads, and SLA compliance across Dynamics 365 customer service data.

  • Marketing campaign performance
    Query lead sources, campaign responses, and conversion data from Dynamics 365 marketing entities to evaluate campaign effectiveness.

  • Activity and interaction history
    Retrieve email logs, call records, meeting notes, and task histories attached to Dynamics 365 records to support relationship management workflows.

  • Revenue and quota reporting
    Generate revenue summaries, quota attainment reports, and win/loss analyses from Dynamics 365 opportunity and order data on demand.

Licensing and activation

Devart MCP Server for Dynamics 365 is distributed as a free single-source MCP server.

To connect to Dynamics 365, the server requires the corresponding Devart ODBC Driver for Dynamics 365, which is a paid product.

A 30-day free trial is available for the Devart ODBC Driver for Dynamics 365.

See the product page and documentation for the latest installation and activation details.

Support

Other Devart connectivity solutions

Source: README.md at commit 7a654f7

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.0LatestSep 23, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.