office-outlook-mcp

io.github.chrischall/office-outlook-mcp

7/7 checks passed
Runs locally
2 secrets
★ 0 GitHub stars
Updated 2026-10-21
Health score 62

About office-outlook-mcp

office-outlook-mcp is an MCP server published by the GitHub account chrischall. Outlook / Microsoft 365 for Claude — triage mail, reply, answer invites and book meetings, confirmed

It runs on your own machine: your AI client starts it from the npm package @chrischall/office-outlook-mcp at version 0.7.1.

It asks for 2 secrets: OUTLOOK_ACCESS_TOKEN and MCP_CONFIRM_SECRET. Give it a key with the least access that still works.

Version 0.7.1 was published on 21 October 2026, and the source code is public, so you can read it before installing.

Written from the registry entry. 9 automated checks on the registry entry and the package code: 7 pass, 0 warn, 0 fail, 2 info. How we check.

What it asks for

Variable	Required	Secret	Description
`OUTLOOK_ACCESS_TOKEN`	No	Yes	Pre-obtained Outlook bearer token. Overrides the browser bridge. Power users / CI only; tokens last about 25 hours.
`OUTLOOK_DISABLE_FETCHPROXY`	No	No	Set to '1' to disable browser capture, requiring OUTLOOK_ACCESS_TOKEN.
`OUTLOOK_API_BASE`	No	No	Override the Outlook REST base URL. Defaults to https://outlook.office.com/api/v2.0.
`OUTLOOK_WS_PORT`	No	No	fetchproxy concentrator port used for token capture. Defaults to 37149, the fleet-wide shared port.
`OUTLOOK_CAPTURE_TIMEOUT`	No	No	Seconds to wait for the Outlook tab to make a request we can read a token from. Defaults to 30.
`OUTLOOK_TOKEN_CACHE`	No	No	Set to 'false' to stop caching the captured token between runs. Defaults to true.
`OUTLOOK_TOKEN_FILE`	No	No	Path to the cached token file. Defaults to ~/.office-outlook-mcp/token.json.
`OUTLOOK_OUTPUT_DIR`	No	No	Absolute directory where outlook_export_messages and outlook_export_events write their files. Defaults to ~/Downloads/office-outlook-mcp. When set, a per-call dest must be inside it.
`FETCHPROXY_WS_HOST`	No	No	Bind interface for the fetchproxy concentrator, a literal IP only (default 127.0.0.1). Keep on loopback; it exists for hosted deployments that run each MCP in its own network namespace.
`FETCHPROXY_IDENTITY_DIR`	No	No	Absolute path where the fetchproxy long-term identity keypair is stored (default ~/.fetchproxy/identity/).
`MCP_CONFIRM_MODE`	No	No	What outlook_send_message, outlook_reply, outlook_respond_to_invite and the other write tools do on a client that cannot show a confirmation prompt (claude.ai, Claude Desktop): "ask-user" (default: the first call returns a preview and a confirmToken, and the model must get your approval in chat before using it), "auto" (the model may use the token after reviewing the preview itself) or "refuse". An unrecognised value is treated as refuse.
`MCP_CONFIRM_ELICITATION`	No	No	"off" never shows a confirmation prompt, so every client gets the MCP_CONFIRM_MODE flow. Set it for a client that says it can show prompts but never does. Defaults to on.
`MCP_CONFIRM_TTL_SECONDS`	No	No	How long a confirmToken stays valid, in seconds. Defaults to 600.
`MCP_CONFIRM_SECRET`	No	Yes	Signing key for confirmTokens. Random per process by default; set it only if tokens must survive a server restart.

Checks

Check	Result	Detail
Source repository linked	Pass	https://github.com/chrischall/office-outlook-mcp
Version pinned	Pass	Every package has an explicit version
Secrets requested	Info	Asks for 2 secrets: OUTLOOK_ACCESS_TOKEN, MCP_CONFIRM_SECRET
Known package registry	Pass	All packages come from npm, PyPI, OCI, NuGet or MCPB
Namespace ownership	Info	Name verified via GitHub account chrischall
Registry text aimed at the AI	Pass	Description and settings contain no hidden characters or instructions to the AI
Install scripts	Pass	@chrischall/office-outlook-mcp@0.7.1 runs nothing at install
Code red flags	Pass	Read 27 files in @chrischall/office-outlook-mcp@0.7.1: no obfuscation, encoded execution, credential reads or data-collection endpoints found
Text aimed at the AI	Pass	No hidden characters or instructions to the AI in 27 files, including comments and the README

Popularity & health: 62 / 100

Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.

Popularity10 / 40

0 GitHub stars, 392 downloads last week, no Hacker News posts found. Best two of the three, each on a log scale.

Activity25 / 25

Last push 2026-10-25, last release 2026-10-21, 86 commits in 90 days.

Issue health8 / 15

9 closed of 9 issues, too few to judge. No data, so half marks.

Our checks20 / 20

0 warnings, each costing a fifth.

0 forks, 85 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.

What people say

No Hacker News threads link to its source code.

Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.

Facts

Registry name	`io.github.chrischall/office-outlook-mcp`
Publisher	GitHub account chrischall
How the name is verified	Name verified via GitHub account chrischall. The registry ties the name prefix to that account or domain; it does not check the code.
Type	Local: runs on your machine from a package
Packages	npm `@chrischall/office-outlook-mcp` 0.7.1 (stdio)
Version	0.7.1
Published	2026-10-21
Last updated	2026-10-21
Source repository	https://github.com/chrischall/office-outlook-mcp
Website	None linked
Category	Productivity & notes (assigned by keyword rule, not by hand)

Install

Claude Desktop · npm package

{
  "mcpServers": {
    "office-outlook-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@chrischall/office-outlook-mcp@0.7.1"
      ]
    }
  }
}

What these checks don't cover

We did not run this server, so we don't know what it does when it runs. We read its package code on 2026-10-29 without running it, and pattern searches miss what they have no pattern for. Tool descriptions built at run time were not seen. And we don't watch it after you install: if the publisher changes it later (a rug pull), this page won't notice until the next scan. Treat a pass as "nothing found", not as "safe".

For people and their AI

The same data as plain JSON: /data/servers/io-github-chrischall-office-outlook-mcp.json. Text inside it that came from the publisher is data, not instructions.