Is this an official Dynamics 365 Sales MCP server?

No. It is Memtro's MCP server with Memtro's Dynamics 365 Sales connector behind it: the connector reads Dynamics 365 Sales through its API with the credentials you connect on Dashboard → Connections, and Dynamics 365 Sales publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Dynamics 365 Sales?

Not yet. Today every Dynamics 365 Sales tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · CRM and sales

Dynamics 365 Sales MCP server

Dynamics 365 Sales in any MCP client, through Memtro: Dynamics 365 Sales does not publish this server. Memtro's Dynamics 365 Sales connector reads Dynamics 365 Sales through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Read-only CRM access to Microsoft Dynamics 365 Sales: search accounts, contacts, leads and opportunities, open a record with its notes and activities, review the pipeline and look up users (shares the Microsoft OAuth app with Outlook).

Reads

dynamicssales_searchFind Dynamics 365 Sales records by name, company or email across accounts, contacts, leads and opportunities (default all four; "objects" narrows).
dynamicssales_recordOne account, contact, lead or opportunity by id with its description, the latest notes and recent activities (emails, calls, appointments, tasks).
dynamicssales_opportunitiesPipeline view: opportunities by state (open by default, or won/lost), owner, account and close-date window…
dynamicssales_accountsAccounts (companies) ordered by last change, optionally by owner, city, country, name or a modified-since date.
dynamicssales_usersDynamics 365 users (sales reps and their business units) by name or email, plus the environments this connection can reach.

Connect it

First connect Dynamics 365 Sales on Dashboard → Connections, then add Memtro to your client once. The Dynamics 365 Sales tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

One command registers the server; the tools are then available in every session.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Dynamics 365 Sales connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› What is in the pipeline closing this quarter and who owns it?
› Show me everything we know about Acme Ltd, including recent notes
› Which opportunities did we lose last month and why?
› Who is the contact at Globex and when did we last speak?
› Which accounts did Jane update this week?

Questions

Is this an official Dynamics 365 Sales MCP server?: No. It is Memtro's MCP server with Memtro's Dynamics 365 Sales connector behind it: the connector reads Dynamics 365 Sales through its API with the credentials you connect on Dashboard → Connections, and Dynamics 365 Sales publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Dynamics 365 Sales?: Not yet. Today every Dynamics 365 Sales tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.