dynamics-365-mcp-server-by-cdata

What is dynamics-365-mcp-server-by-cdata?

dynamics-365-mcp-server-by-cdata is a read-only Model Context Protocol (MCP) server that enables large language models (LLMs) like Claude Desktop to query live data from Microsoft Dynamics 365. It wraps the CData JDBC Driver for Dynamics 365, exposing the CRM data as a relational SQL model so AI clients can retrieve information through natural language questions without writing SQL.

How to use dynamics-365-mcp-server-by-cdata?

Clone the repository, build the JAR with mvn clean install, download and license the CData JDBC Driver for Dynamics 365, then create a .prp configuration file with your JDBC connection string. Finally, add the server to your MCP client’s configuration (e.g., claude_desktop_config.json) pointing to the JAR and the .prp file. The server communicates via stdio, so the client must run on the same machine. Once configured, you can ask the AI questions like “What is the correlation between my closed won opportunities and the account industry?”

Key features of dynamics-365-mcp-server-by-cdata

• Read-only access to Dynamics 365 data via MCP.
• No SQL required: LLMs query data in natural language.
• Built on the CData JDBC Driver for Dynamics 365.
• Exposes three tools: get_tables, get_columns, and run_query.
• Tools return results in CSV format with header rows.
• Supports any MCP client that can run a local server.

Use cases of dynamics-365-mcp-server-by-cdata

• Ask an AI assistant for real-time sales or support ticket summaries.
• Perform cross-table analysis (e.g., correlate opportunities with account industry).
• Retrieve live CRM records without writing or exposing SQL queries.
• Enable natural-language reporting for non-technical team members.

FAQ from dynamics-365-mcp-server-by-cdata

Is this server read-only?

Yes, this version is explicitly read-only. For full create, update, delete, and action capabilities, CData offers a separate beta MCP Server that includes write operations and simplified setup.

What runtime or dependencies are required?

You need Java to run the server, the CData JDBC Driver for Dynamics 365 (requires licensing), and an MCP client (e.g., Claude Desktop) on the same machine. The server is built using Maven.

Where does the data live during a query?

Data is never stored by the server. The server queries Dynamics 365 live through the JDBC Driver and returns results directly to the client; all processing happens in memory on the local machine.

What are the known limitations of dynamics-365-mcp-server-by-cdata?

The server is read-only, only supports SELECT queries, and uses stdio transport — so the client must run on the same machine as the server. It also requires manual configuration of the JDBC connection string.

How does authentication work for the data source?

Authentication is handled by the CData JDBC Driver when building the connection string. For OAuth-based sources, the driver opens a browser window for you to authenticate. The resulting connection string is stored in the .prp file.