Outlook Assistant MCP Server

What the code does

We read the source, 7 d ago · rules 995398eba69f

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

      fs.writeFileSync(outputPath, buffer);

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    current = path.join(current, segment);

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add outlook-assistant -- npx -y @littlebearapps/outlook-assistant

{
  "mcpServers": {
    "outlook-assistant": {
      "command": "npx",
      "args": [
        "-y",
        "@littlebearapps/outlook-assistant"
      ]
    }
  }
}

[mcp_servers.outlook-assistant]
command = "npx"
args = ["-y", "@littlebearapps/outlook-assistant"]

{
  "mcpServers": {
    "outlook-assistant": {
      "command": "npx",
      "args": [
        "-y",
        "@littlebearapps/outlook-assistant"
      ]
    }
  }
}

{
  "servers": {
    "outlook-assistant": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@littlebearapps/outlook-assistant"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: OUTLOOK_CLIENT_ID (Azure AD application (client) ID. Optional: if it is not set here, supply it at sign-in with the auth tool (action=authenticate clientId=<id>)), OUTLOOK_CLIENT_SECRET (Azure AD application client secret value. Only needed for the browser sign-in flow; the default device-code flow doesn't use it).