Connect Microsoft Dynamics 365 to Claude Code
Make Claude log activities and advance opportunities in Microsoft Dynamics 365. From the terminal, inside the sessions where you already work.
How do you connect Microsoft Dynamics 365 to Claude Code?
Claude Code reaches outside tools through MCP servers. To connect Microsoft Dynamics 365, you add a Microsoft Dynamics 365 MCP server: a small hosted service that exposes Microsoft Dynamics 365's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Microsoft Dynamics 365 account. No API keys pasted into config files.
claude mcp add --transport http dynamics-365 https://your-connector-url/mcpThen run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.
What can Claude Code do in Microsoft Dynamics 365 once connected?
Full read-write Dynamics 365 access lets Claude advance opportunity stages and amounts, log calls and emails as activities, create leads and contacts, and keep records current as work happens. The CRM hygiene and pipeline updates that used to mean manual data entry happen where the record already lives.
- Advance an opportunity's stage, estimated value, or close date as a deal progresses
- Log a phone call, email, or appointment as an activity on the right account or contact
- Create a new lead or contact and link it to the right account
- Update fields on accounts and contacts to keep records current
- Create or update a case and route it to the right queue
- Find records matching a query and propose batched field updates
One connector, every Claude surface
The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Microsoft Dynamics 365 access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.
Build it yourself, or have it built?
If you live in the terminal, you can absolutely write your own MCP server against the Microsoft Dynamics 365 API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Microsoft Dynamics 365 changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Microsoft Dynamics 365 connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.
Frequently asked questions
Does the same Microsoft Dynamics 365 connector work in claude.ai and Claude Code?
Do I need to host or maintain anything myself?
Is it safe to give a coding agent write access to Microsoft Dynamics 365?
More on the Microsoft Dynamics 365 connector
Tell us what you run. We'll build the connector.
Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.