D365 MCP Server

D365 MCP server exists for a simple reason — assistants are far more useful when they can act on D365 directly instead of describing what you should do. Give your coding agent direct access to Dynamics 365 / Dataverse metadata and web resources through a Model Context Protocol (MCP) server.

What you get

• search_entities: Search Dataverse tables by logical or display name
• get_entity_plugins: List plugin steps registered for a specific entity
• find_system_jobs: Find system jobs (async operations) with flexible filters (failed by default)
• health_check_environment: Run a quick environment health summary using system jobs and plugin traces
• search_webresources: Find web resources by name/display name
• get_webresource_content: Read decoded web resource content by ID or name

Setting it up

Installation goes through your MCP client rather than a global install: point it at pnpm on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

What the assistant can call

Once D365 is connected, these are the calls the assistant has available:

• search_entities — Search Dataverse tables by logical or display name
• get_entity_plugins — List plugin steps registered for a specific entity
• find_system_jobs — Find system jobs (async operations) with flexible filters (failed by default)
• health_check_environment — Run a quick environment health summary using system jobs and plugin traces
• search_webresources — Find web resources by name/display name
• get_webresource_content — Read decoded web resource content by ID or name
• TENANT_ID — CLIENT_ID
• CLIENT_SECRET — DYNAMICS_365_URL (example: https://orgname.crm.dynamics.com)
• Windows — The Windows tool exposed by this server

Configuration and credentials

You will need 7 environment variables: TENANT_ID, CLIENT_ID, CLIENT_SECRET, DYNAMICS_365_URL, YOUR_TENANT_ID, YOUR_CLIENT_ID, YOUR_CLIENT_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js 18+ (recommended: latest LTS) - A Dynamics 365 / Dataverse environment URL - Microsoft Entra app registration with access to your Dataverse org - Tenant ID, Client ID, and Client Secret Required environment variables: - TENANT_ID - CLIENT_ID - CLIENT_SECRET - DYNAMICS_365_URL (example: https://orgname.crm.dynamics.com) Optional logging variables: - MCP_LOG_FILE (default

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch D365.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the d365 mcp server does with a few real requests.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. D365's toolset — search_entities, get_entity_plugins, find_system_jobs and 6 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.