ms-calendar-mcp

What does ms-calendar-mcp need from you?

Configuration only — Declares config values but no credentials.

• MICROSOFT_CLIENT_IDoptionalEnvironment variable

  Entra ID application (client) ID for the public client app used to sign in. Run `npx -y ms-calendar-mcp login` once to cache a refresh token.

Pass secrets through your shell environment rather than committing them into a config file.

What tools does ms-calendar-mcp expose?

This server runs as a local package. We only query remote servers for their tool list — asking this one would mean executing it, so its tools are listed in the documentation below.

What the code can do

Read from the published package source — never executed. Parsed 1 of 1 source file.

This server can run other programs on your machine, read and write files and make network requests.

• Runs other programsImports Node's child_process module, which starts other programs on your machine with your user's permissions.
• Reads and writes filesImports Node's fs module. Nothing in the package limits this to a particular folder — scoping is whatever you configure when you launch it.
• Makes network requestsOpens network connections or calls fetch, so data it handles can leave your machine and it can pull data in.
• Reads environment variablesReads process.env. That is how it picks up the API keys you configure — and it is not restricted to only those variables.
• Reads system informationImports os or v8 to read machine details such as hostname, platform or home directory.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

• Last commit 4 months ago — Actively maintained.
• 0 GitHub stars — Very little community usage so far.

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

• Maintenance30%84%

  Last commit 142 days ago.

• Adoption20%0%

  0 stars.

• Transparency20%75%

  3/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✗ discoverable tool list.

• Provenance15%100%

  Package and registry entry point at the same repository.

• Packaging15%100%

  Publishes a pinned version (1.0.1).

microsoft-mcp/
├── apps/                       # one MCP server per Microsoft 365 product
│   ├── calendar/
│   ├── contacts/
│   ├── onedrive/
│   ├── outlook/
│   └── sharepoint/
│       └── src/
│           ├── tools.ts        # declarative tool definitions (schema + handler)
│           └── index.ts        # run({ name, version }, tools)
└── packages/                   # shared building blocks
    ├── core/                   # MCP server bootstrap + dual transport (stdio / HTTP)
    ├── graph/                  # Microsoft Graph HTTP client
    ├── validation/             # id / path / query sanitizers
    └── logger/                 # structured JSON logging (stderr-only — stdio-safe)

// apps/calendar/src/index.ts
import { run } from "@microsoft-mcp/core";
import { tools } from "./tools.js";

void run({ name: "microsoft-calendar", version: "1.0.0", title: "Microsoft Calendar" }, tools);

// a single tool
defineTool({
  name: "get_event",
  description: "Get a single calendar event by ID.",
  inputSchema: { event_id: z.string().describe("Event ID") },
  confirmationPolicy: "never",
  handler: ({ graph }, { event_id }) => {
    validateId(event_id, "event_id");
    return graph.request("GET", `/me/events/${event_id}`);
  },
});

Excerpt — the full document is on GitHub.

Maintain ms-calendar-mcp? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

[![ms-calendar-mcp on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/io-github-0xka13b-ms-calendar-mcp)](https://mcp-skills-hub.vercel.app/mcps/io-github-0xka13b-ms-calendar-mcp)