Outlook

io.github.mcp-zPublished by GitHub account mcp-zv2.2.3Updated Oct 24, 2026

Outlook integration with OAuth, message search, batch operations, and calendar management

Overview

AI-generated overview

A local MCP server that connects an assistant to Microsoft Outlook for message search, batch operations and calendar management, using Microsoft OAuth.

What you can do
Search and work with Outlook email messages, including batch operations across several messages at once. Manage calendar entries such as events and appointments. Authenticate to Microsoft through OAuth, with configurable client, tenant and redirect settings. Export data to CSV files through a configurable resource store.
When to use it
Useful when you want an assistant to read, search or act on a Microsoft Outlook mailbox and calendar from your own machine, rather than through a hosted service.
Requirements
Runs locally as an npm package via npx, so Node.js is needed. A Microsoft OAuth app registration is required: MS_CLIENT_ID and MS_TENANT_ID are required, and MS_CLIENT_SECRET is optional for public clients. Several optional environment variables configure auth mode, base URL, dynamic client registration, headless login, port, redirect URI and CSV export storage.
Before you install
It handles Microsoft account access through OAuth and may request the client secret MS_CLIENT_SECRET; treat it as sensitive. Batch operations and calendar management can change mailbox and calendar data, so review what the assistant is about to do. CSV exports write files to the location set by RESOURCE_STORE_URI.

Installation

In SourceWeft

  1. Open Outlook in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

3
  1. v2.2.3LatestOct 12, 2026
  2. v2.2.2Oct 10, 2026
  3. v2.2.1Sep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.