Dynamics 365 MCP Server 🚀

What is Dynamics 365 MCP Server 🚀?

The Microsoft Dynamics 365 MCP Server is an MCP server that provides tools to interact with Microsoft Dynamics 365 using the Model Context Protocol (MCP) by Anthropic. It allows users to perform operations such as retrieving user information, accounts, opportunities, and creating or updating accounts from Claude Desktop.

How to use Dynamics 365 MCP Server 🚀?

Clone the repository, install dependencies with npm install, configure environment variables (CLIENT_ID, CLIENT_SECRET, TENANT_ID, D365_URL) in a .env file, compile TypeScript with npm run build, and run the server with node build/index.js. Optionally, register the server with Claude Desktop by editing claude_desktop_config.json.

Key features of Dynamics 365 MCP Server 🚀

• Fetches information about the currently authenticated user.
• Retrieves all accounts from Dynamics 365.
• Fetches opportunities associated with a given account.
• Creates new accounts in Dynamics 365.
• Updates existing accounts in Dynamics 365.

Use cases of Dynamics 365 MCP Server 🚀

• Get user details from Dynamics 365 while using Claude Desktop.
• List all accounts and review them in a chat interface.
• View opportunities linked to a specific account.
• Create and update account records without leaving Claude.
• Automate CRM data management with natural language prompts.

FAQ from Dynamics 365 MCP Server 🚀

What tools does this server provide?

The server provides five tools: get-user-info, fetch-accounts, get-associated-opportunities, create-account, and update-account.

What are the prerequisites to run the server?

You need Node.js (v16+), NPM, a Dynamics 365 instance with API access, and an Azure Active Directory (AAD) application configured for Dynamics 365 APIs.

How do I configure authentication?

Set CLIENT_ID, CLIENT_SECRET, TENANT_ID, and D365_URL in a .env file. The server uses OAuth via Azure AD to authenticate requests.

How can I test the tools?

You can test them by registering the server with Claude Desktop or by using the MCP Inspector tool (npx @modelcontextprotocol/inspector node build/index.js).

Does the server run over HTTP or stdio?

The server communicates over stdio, as indicated by the startup message "Dynamics365 MCP server running on stdio...".