What can you do with this server?

The Dynamics 365 MCP Server enables interaction with Microsoft Dynamics 365 using the Model Context Protocol (MCP). With this server, you can: * Retrieve authenticated user information (get-user-info) * Fetch all accounts from Dynamics 365 (fetch-accounts) * Retrieve opportunities associated with a specific account (get-associated-opportunities) * Create new accounts in Dynamics 365 (create-account) * Update existing accounts in Dynamics 365 using its ID and updated details (update-account)

Which integrations are available for this server?

Manages environment configuration for Dynamics 365 connection credentials including client ID, client secret, tenant ID, and service URL. Provides version control for the codebase, allowing collaborative development through clone, branch, and pull request operations. Hosts the repository for the MCP server code, enabling collaborative development and issue tracking. Uses Node.js runtime environment (v16+) to execute the MCP server that connects to Dynamics 365. Manages package dependencies for the project, including the Model Context Protocol SDK. Displays status badges in the README showing Node.js version, TypeScript version, MCP status, and license information. Implements the server using TypeScript 4.x for type-safe interaction with the Dynamics 365 APIs.

How do I use Dynamics 365 MCP Server?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Dynamics 365 MCP Server show me all accounts" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

en es ja ko zh

Dynamics 365 MCP Server

by srikanth-paladugula

Overview Schema Related Servers Score Discussions

TypeScript

Remote

Dynamics 365 MCP Server 🚀

Node.js TypeScript MCP License

Overview

The Microsoft Dynamics 365 MCP Server is a MCP server that provides tools to interact with Microsoft Dynamics 365 using the Model Context Protocol(MCP) by Anthorpic. It allows users to perform various operations such as retrieving user information, accounts, opportunities associated with an account, create and update accounts from Claude Desktop.

This project uses the @modelcontextprotocol/sdk library to implement the MCP server and tools, and it integrates with Dynamics 365 APIs for data operations.

Related MCP server: Dataverse MCP Server

List of Tools 🛠️

Tool Name	Description	Input	Output
`get-user-info`	Fetches information about the currently authenticated user.	None	User details including name, user ID, and business unit ID.
`fetch-accounts`	Fetches all accounts from Dynamics 365.	None	List of accounts in JSON format.
`get-associated-opportunities`	Fetches opportunities associated with a given account.	`accountId` (string, required)	List of opportunities in JSON format.
`create-account`	Creates a new account in Dynamics 365.	`accountData` (object, required) containing account details.	Details of the created account in JSON format.
`update-account`	Updates an existing account in Dynamics 365.	`accountId` (string, required), `accountData` (object, required) containing updated details.	Details of the updated account in JSON format.

Prerequisites 📝

Before setting up the project, ensure you have the following installed:

Node.js (v16 or higher)
NPM (Node Package Manager)
A Dynamics 365 instance with API access
Azure Active Directory (AAD) application configured for Dynamics 365 API access

Configuration Steps ⚙️

Follow these steps to set up and run the project locally:

1. Clone the Repository

git clone https://github.com/your-repo/dynamics365-mcp-server.git
cd dynamics365-mcp-server

2. Install Dependencies

npm install

3. Configure Environment Variables

Create a .env file in the root of the project and add the following variables:

CLIENT_ID=your-client-id
CLIENT_SECRET=your-client-secret
TENANT_ID=your-tenant-id
D365_URL=https://your-org.crm.dynamics.com

4. Compile TypeScript Files

npm run build

4. Run MCP Server

node build\index.js

You should see the following output:

Dynamics365 MCP server running on stdio...

5. (Optional) Register your MCP Server with Claude Desktop

Install Claude Desktop
Navigate to Settings > Developer > Edit Config
Edit claude_desktop_config.json

{
    "mcpServers": {
        "Dynamics365": {
            "command": "node",
            "args": [
                "<Path to your MCP server build file ex: rootfolder/build/index.js>"
            ],
            "env": {
                "CLIENT_ID": "<D365 Client Id>",
                "CLIENT_SECRET": "<D365 Client Secret>",
                "TENANT_ID": "<D365 Tenant ID>",
                "D365_URL": "Dynamics 365 url"
            }
        }
    }
}

Restart Claude Desktop
Now you should be able to see the server tools in the prompt window
Let's test a prompt by invoking tool - get-user-info

6. (Optional) Test tools using MCP Interceptor

Run following command in terminal

npx @modelcontextprotocol/inspector node build/index.js

Interceptor commange

Go to 🔍 http://localhost:5173 🚀
Now you can connect to server and terst all the tools!!

Debugging 🐛

If you encounter issues, ensure the following:

The .env file is properly configured.
The Azure AD application has the necessary permissions for Dynamics 365 APIs.
The Dynamics 365 instance is accessible from - your environment.
You can also add debug logs in the code to trace issues. For example:

console.error("Debugging: Loaded environment variables:", process.env);

Contributing 🤝

Contributions are welcome! Feel free to submit a pull request or open an issue for any bugs or feature requests.

To contribute:

Fork the repository.
Create a new branch for your feature or bug fix.
Commit your changes and submit a pull request.
We appreciate your contributions! 😊

Available Tools

5 tools

create-accountC

Create a new account in Dynamics 365

ParametersJSON Schema

Name	Required	Description	Default
`accountData`	Yes

TDQS

C2.7/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Create' implies a write operation, but lacks details on permissions, side effects (e.g., if it overwrites existing accounts), error handling, or response format. This is inadequate for a mutation tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, direct sentence with no wasted words, making it highly concise and front-loaded. It efficiently communicates the core action without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a creation tool with no annotations, 0% schema coverage, no output schema, and a nested object parameter, the description is insufficient. It lacks details on parameter semantics, behavioral traits, and expected outcomes, leaving significant gaps for the agent to operate effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 1 parameter ('accountData') with 0% description coverage, and the tool description provides no information about what 'accountData' should contain (e.g., required fields like name, email, or structure). This leaves the parameter completely undocumented, failing to compensate for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Create') and the resource ('a new account in Dynamics 365'), making the purpose understandable. It distinguishes from siblings like 'fetch-accounts' (read) and 'update-account' (modify), but doesn't explicitly differentiate from other potential creation tools, keeping it at a 4 rather than a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'update-account' or prerequisites for account creation. The description merely states what it does without context, leaving the agent to infer usage scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

fetch-accountsB

Fetch accounts from Dynamics 365

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'fetch' which implies a read operation, but doesn't specify whether this requires authentication, has rate limits, returns paginated results, or what format the data comes in. This leaves significant gaps for a tool interacting with an external system like Dynamics 365.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that states exactly what the tool does with zero wasted words. It's appropriately sized for a simple tool and front-loads the essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool that fetches data from an external system like Dynamics 365 with no annotations and no output schema, the description is incomplete. It doesn't explain what kind of accounts are fetched, whether there are filters or sorting options, what the return format looks like, or any error conditions. The agent would need to guess these important details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so the schema already fully documents the absence of parameters. The description appropriately doesn't add parameter information beyond what's in the schema, maintaining a baseline score of 4 for tools with no parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Fetch accounts from Dynamics 365' clearly states the action (fetch) and resource (accounts from Dynamics 365), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'get-associated-opportunities' which might also fetch account-related data, so it misses the highest score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'create-account' or 'update-account'. It doesn't mention any context, prerequisites, or exclusions, leaving the agent to infer usage from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get-associated-opportunitiesC

Fetch opportunities for a given account from Dynamics 365

ParametersJSON Schema

Name	Required	Description	Default
`accountId`	Yes

TDQS

C2.9/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'fetch' (implying a read operation) but doesn't cover critical aspects like authentication requirements, rate limits, error handling, or what the return format looks like (e.g., list of opportunities with fields). This leaves significant gaps for an agent to use it effectively.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words. It's front-loaded with the core purpose, making it easy to scan and understand quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of fetching data from Dynamics 365, no annotations, no output schema, and low schema coverage, the description is incomplete. It lacks details on behavioral traits, parameter usage, and expected outputs, which are essential for an agent to invoke this tool correctly in a real-world context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It mentions 'for a given account,' which hints at the 'accountId' parameter's purpose, but doesn't explain the parameter's format (e.g., GUID), source, or constraints. This adds minimal value beyond the schema's structural definition, aligning with the baseline for low coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('fetch') and target resource ('opportunities for a given account from Dynamics 365'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'fetch-accounts' or 'get-user-info' in terms of scope or relationship, which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description implies it's for fetching opportunities linked to an account, but it doesn't specify prerequisites, exclusions, or compare it to other tools like 'fetch-accounts' for broader account data.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get-user-infoC

Get user info from Dynamics 365

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

C2.8/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It states a read operation ('Get'), implying it's likely safe, but doesn't disclose behavioral traits such as authentication requirements, rate limits, error conditions, or what happens if no user is found. This leaves significant gaps in understanding how the tool behaves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and appropriately sized for a simple tool, though it could be slightly more informative without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and a simple but vague purpose, the description is incomplete. It doesn't explain what 'user info' includes, how results are returned, or any constraints, making it inadequate for an agent to use effectively without additional context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param details, which is appropriate here, but it could hint at implicit parameters (e.g., user ID context), though not required. Baseline is 4 for zero parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the action ('Get') and resource ('user info from Dynamics 365'), which provides a basic understanding of purpose. However, it's vague about what specific user information is retrieved and doesn't differentiate from sibling tools like 'fetch-accounts' or 'create-account', leaving ambiguity about scope and distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, context (e.g., when user info is needed over account data), or exclusions, leaving the agent without usage direction beyond the basic purpose.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

update-accountC

Update an existing account in Dynamics 365

ParametersJSON Schema

Name	Required	Description	Default
`accountId`	Yes
`accountData`	Yes

TDQS

C2.7/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Update' implies a mutation, but fails to mention critical details like required permissions, whether changes are reversible, error handling, or rate limits. This leaves significant gaps in understanding the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words. It is front-loaded with the core action and resource, making it easy to parse quickly, which is ideal for conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a mutation tool with no annotations, 0% schema coverage, and no output schema, the description is incomplete. It lacks details on parameters, behavioral traits, return values, and usage context, making it inadequate for safe and effective tool invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning the schema provides no parameter details. The description adds no information about the parameters 'accountId' (e.g., format, source) or 'accountData' (e.g., allowed fields, structure), failing to compensate for the lack of schema documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Update') and resource ('an existing account in Dynamics 365'), making the tool's purpose understandable. However, it doesn't differentiate from sibling tools like 'create-account' or 'fetch-accounts' beyond the basic verb distinction, which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like 'create-account' for new accounts or 'fetch-accounts' for reading. It lacks context on prerequisites, such as needing an existing account ID, or exclusions, leaving the agent without clear usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.3/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: create-account and update-account handle account creation and modification, fetch-accounts retrieves accounts, get-associated-opportunities fetches related opportunities, and get-user-info handles user data. The descriptions clearly differentiate the target resources and actions.

Naming Consistency4/5

The tools follow a consistent verb-noun pattern with hyphens (e.g., create-account, fetch-accounts), except for get-user-info which uses 'info' instead of a more specific noun like 'user'. This minor deviation slightly affects consistency, but the overall pattern is clear and readable.

Tool Count5/5

With 5 tools, the server is well-scoped for managing Dynamics 365 accounts and related data. Each tool earns its place by covering essential CRUD operations for accounts and providing useful related functions like fetching opportunities and user info, without being overly sparse or bloated.

Completeness4/5

The toolset provides solid coverage for account management with create, fetch, and update operations, plus useful extensions for opportunities and user info. A minor gap exists in lacking a delete-account tool, which agents might need to work around, but core workflows are well-supported.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Reddit Discussion

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Artificial Wit AI
com.artificialwit
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
ERP Systems CRM Knowledge & Memory
2
Microsoft MCP Server for Enterprise
io.github.microsoft
Official Microsoft MCP Server to query Microsoft Entra data using natural language
Search Security
252
Relm CRM A
com.relmcrm
API-first CRM for LLMs - contacts, companies, deals and activities over a native MCP server.
CRM AI & Machine Learning
412
hithereiamaliff-mcp-nextcloudOAuth
ai.smithery
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Cloud Storage File Systems Workplace & Productivity
237

Related MCP Servers

PowerPlatform MCP
Developer Tools Databases
michsob
A
license
B
quality
C
maintenance
A Model Context Protocol (MCP) server that provides intelligent access to PowerPlatform/Dataverse entities and records. This tool offers context-aware assistance, entity exploration and metadata access.
Updated 5 days ago (2026-08-30 11:49 UTC)
38
68
42
MIT
Dataverse MCP Server
CRM Databases
Ajscheuer
A
license
Not graded
quality
D
maintenance
A Model Context Protocol server that enables CRUD operations and querying on Microsoft Dataverse through natural language.
Updated a year ago (2025-05-29 13:14 UTC)
21
MIT
OpenText Process Automation
App Automation ERP Systems
amitagl27
A
license
Not graded
quality
C
maintenance
A Model Context Protocol server that lets Claude and any other MCP-compatible client work with an OpenText AppWorks Platform tenant in plain English.
Updated a month ago (2026-07-21 17:37 UTC)
MIT
Business Central MCP Workshop
ERP Systems Databases
javiarmesto
F
license
Not graded
quality
D
maintenance
MCP server that integrates with Microsoft Dynamics 365 Business Central, enabling querying of customers, items, and sales orders through natural language commands in Claude Desktop.
Updated 9 months ago (2025-11-23 17:00 UTC)
10

Appeared in Searches

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/srikanth-paladugula/mcp-dynamics365-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server