home / mcp / dynamics 365 mcp server
This read-only MCP Server allows you to connect to Dynamics 365 data from Claude Desktop through CData JDBC Drivers. For full CRUD support, check out the first managed MCP platform: CData Connect AI (https://www.cdata.com/ai/).
Configuration
View docs{
"mcpServers": {
"cdatasoftware-dynamics-365-mcp-server-by-cdata": {
"command": "PATH\\\\TO\\\\java.exe",
"args": [
"-jar",
"PATH\\\\TO\\\\CDataMCP-jar-with-dependencies.jar",
"PATH\\\\TO\\\\dynamics-365.prp"
]
}
}
}You can query live Dynamics 365 data through a local, read-only MCP server that wraps the CData JDBC Driver. This enables natural-language requests to retrieve up-to-date information from Dynamics 365 without writing SQL, making it ideal for AI assistants and LLM-powered workflows on a single machine.
You will run the MCP server on your machine and connect your MCP client (for example Claude Desktop) to it. The server exposes a small set of MCP tools that let your client discover which tables exist, view their columns, and run read-only queries. Use natural-language questions like “What is the open opportunity count by account industry?” and the client will translate those into the available MCP tools behind the scenes. No SQL is required for common questions, and you’ll be querying live data from Dynamics 365 through the CData JDBC Driver.
# Prerequisites
# - Java (JDK 8+)
# - Maven (to build the MCP server)
# 1. Clone the project
git clone https://github.com/cdatasoftware/dynamics-365-mcp-server-by-cdata.git
cd dynamics-365-mcp-server-by-cdata
# 2. Build the MCP server
mvn clean install
# This produces: CDataMCP-jar-with-dependencies.jar
# 3. Install the CData JDBC Driver for Dynamics 365
# - Download from the CData site and install according to your OS
# 4. License the JDBC Driver
# - Locate the lib directory in the installation (example paths below)
# - Run the license command and provide your name, email, and license key
# 5. Configure your connection to Dynamics 365
# - Run the connection string utility to generate a JDBC URL
# - Save the resulting connection string for use in the .prp file
# 6. Create the MCP connection file
# - Create a dynamics-365.prp with the required properties described in the guide
# - Example properties appear in the source setup
# 7. Run the MCP server locally (stdio)
java -jar /PATH/TO/CDataMCP-jar-with-dependencies.jar /PATH/TO/dynamics-365.prpThe MCP server runs on your local machine and communicates with your MCP client via stdio. Ensure you start and stop your MCP client cleanly so the server can be discovered and used by the client. If you update any connection details, re-run the client or restart the MCP server to apply changes.
If you cannot see the MCP server in your client, fully quit the client and restart it so the server appears. Verify that the JDBC connection string is correct by re-running the Connection String utility and using the resulting URL in your .prp file. If problems persist, verify your data source connectivity and consult CData support or community resources.
This MCP server is read-only. You do not need to call any internal tools directly; instead, ask your client questions about the Dynamics 365 data. Available tooling includes getting the list of tables, listing columns for a table, and running a SELECT query. You can use the built-in tools to retrieve data and compose answers without writing SQL.
Retrieves a list of tables available in the Dynamics 365 data source. Output is CSV with column headers on the first line.
Retrieves a list of columns for a specified table. Output is CSV with column headers on the first line.
Executes a SQL SELECT query against the configured Dynamics 365 data source.