Is this an official Microsoft Entra ID MCP server?

No. It is Memtro's MCP server with Memtro's Microsoft Entra ID connector behind it: the connector reads Microsoft Entra ID through its API with the credentials you connect on Dashboard → Connections, and Microsoft Entra ID 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 Microsoft Entra ID?

Not yet. Today every Microsoft Entra ID 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 · People and HR

Microsoft Entra ID MCP server

Microsoft Entra ID in any MCP client, through Memtro: Microsoft Entra ID does not publish this server. Memtro's Microsoft Entra ID connector reads Microsoft Entra ID 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 directory from Microsoft Entra ID (Azure AD): people with titles, departments and managers, groups and memberships, recent sign-ins and directory audit events (shares the Microsoft OAuth app with Outlook).

Reads

entra_peopleFind people in the Entra ID directory by name or email (prefix match), department or job title, with manager for the first ten results.
entra_personOne person by id, email/UPN or exact display name: profile, manager, direct reports and group memberships.
entra_groupsGroups by name (Microsoft 365, security, distribution or dynamic), or one group by id / exact name with its owners and members.
entra_signinsRecent sign-ins (newest first): for one user, or across the tenant with failures_only for failed attempts; each with app, IP, location…
entra_auditDirectory audit log (newest first): user, group, application, role and policy changes with who made them and what changed.

Connect it

First connect Microsoft Entra ID on Dashboard → Connections, then add Memtro to your client once. The Microsoft Entra ID 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 Microsoft Entra ID 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

› Who does Priya report to and who is on her team?
› List everyone in the Finance department with their titles
› Which security groups is Sam a member of?
› Were there failed sign-ins for the CFO this week?
› Who was added to the Global Administrators role recently?

Questions

Is this an official Microsoft Entra ID MCP server?: No. It is Memtro's MCP server with Memtro's Microsoft Entra ID connector behind it: the connector reads Microsoft Entra ID through its API with the credentials you connect on Dashboard → Connections, and Microsoft Entra ID 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 Microsoft Entra ID?: Not yet. Today every Microsoft Entra ID 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.