Minerva MCP — Microsoft 365 & Azure

Minerva MCP — Microsoft 365 & Azure runs locally from a Node.js package published to the npm registry: minerva-mcp version 0.4.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y minerva-mcp@0.4.2. It reads these environment variables: AZURE_TENANT_ID, AZURE_CLIENT_ID, AZURE_CLIENT_SECRET (secret) and MINERVA_SHAREPOINT_URL; set them in the client's configuration for this server. Required arguments: --stdio.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "minerva-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "minerva-mcp@0.4.2"
      ],
      "env": {
        "AZURE_TENANT_ID": "<value>",
        "AZURE_CLIENT_ID": "<value>",
        "AZURE_CLIENT_SECRET": "<secret>",
        "MINERVA_SHAREPOINT_URL": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect