Outlook / Microsoft 365 for Claude — triage mail, reply, answer invites and book meetings, confirmed
Office-outlook-mcp is an MCP integration. Outlook / Microsoft 365 for Claude — triage mail, reply, answer invites and book meetings, confirmed.
The published npm package is @chrischall/office-outlook-mcp, version 0.5.2. Its declared MCP transport is stdio.
The package declares OUTLOOK_ACCESS_TOKEN: Pre-obtained Outlook bearer token. Overrides the browser bridge. Power users / CI only; tokens last about 25 hours.; OUTLOOK_DISABLE_FETCHPROXY: Set to '1' to disable browser capture, requiring OUTLOOK_ACCESS_TOKEN.; OUTLOOK_API_BASE: Override the Outlook REST base URL. Defaults to https://outlook.office.com/api/v2.0.; OUTLOOK_WS_PORT: fetchproxy concentrator port used for token capture. Defaults to 37149, the fleet-wide shared port.; OUTLOOK_CAPTURE_TIMEOUT: Seconds to wait for the Outlook tab to make a request we can read a token from. Defaults to 30.; OUTLOOK_TOKEN_CACHE: Set to 'false' to stop caching the captured token between runs. Defaults to true.; OUTLOOK_TOKEN_FILE: Path to the cached token file. Defaults to ~/.office-outlook-mcp/token.json.; FETCHPROXY_WS_HOST: 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: Absolute path where the fetchproxy long-term identity keypair is stored (default ~/.fetchproxy/identity/).; MCP_CONFIRM_MODE: What outlook_send_mail, 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: "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: How long a confirmToken stays valid, in seconds. Defaults to 600.; MCP_CONFIRM_SECRET: Signing key for confirmTokens. Random per process by default; set it only if tokens must survive a server restart..
Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.
View the publisher’s registry entry · Project repository. This profile uses version 0.5.2 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.
Browse related email & inbox management MCP servers for tools that cover the same kind of work.
| Variable | Description | Required |
|---|---|---|
| OUTLOOK_ACCESS_TOKEN | Pre-obtained Outlook bearer token. Overrides the browser bridge. Power users / CI only; tokens last about 25 hours. | Check documentation |
| OUTLOOK_DISABLE_FETCHPROXY | Set to '1' to disable browser capture, requiring OUTLOOK_ACCESS_TOKEN. | Check documentation |
| OUTLOOK_API_BASE | Override the Outlook REST base URL. Defaults to https://outlook.office.com/api/v2.0. | Check documentation |
| OUTLOOK_WS_PORT | fetchproxy concentrator port used for token capture. Defaults to 37149, the fleet-wide shared port. | Check documentation |
| OUTLOOK_CAPTURE_TIMEOUT | Seconds to wait for the Outlook tab to make a request we can read a token from. Defaults to 30. | Check documentation |
| OUTLOOK_TOKEN_CACHE | Set to 'false' to stop caching the captured token between runs. Defaults to true. | Check documentation |
| OUTLOOK_TOKEN_FILE | Path to the cached token file. Defaults to ~/.office-outlook-mcp/token.json. | Check documentation |
| FETCHPROXY_WS_HOST | 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. | Check documentation |
| FETCHPROXY_IDENTITY_DIR | Absolute path where the fetchproxy long-term identity keypair is stored (default ~/.fetchproxy/identity/). | Check documentation |
| MCP_CONFIRM_MODE | What outlook_send_mail, 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. | Check documentation |
| MCP_CONFIRM_ELICITATION | "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. | Check documentation |
| MCP_CONFIRM_TTL_SECONDS | How long a confirmToken stays valid, in seconds. Defaults to 600. | Check documentation |
| MCP_CONFIRM_SECRET | Signing key for confirmTokens. Random per process by default; set it only if tokens must survive a server restart. | Check documentation |
Store entities, relations and observations in a local knowledge graph with the reference Memory MCP server.
Connect the Notion MCP server to search workspace content and work with pages and databases through Notion’s hosted OAuth service.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.