MCP Outlook - Microsoft Outlook Integration for Claude

Created By
asirulnika year ago
MCP Server and CLI for Microsoft Outlook integration
Overview

What is MCP Outlook?

MCP Outlook is a Model Context Protocol (MCP) server that integrates Microsoft Outlook functionalities such as mail, drafts, folders, and calendar with AI assistants like Claude.

How to use MCP Outlook?

To use MCP Outlook, you can operate it in CLI mode for direct commands or configure it as an MCP server for integration with Claude Desktop. Installation involves cloning the repository, installing dependencies, and setting up environment variables for Microsoft Graph API credentials.

Key features of MCP Outlook?

  • Mail operations: List, read, move, and copy emails with filtering capabilities.
  • Folder management: Create, move, and rename mail folders.
  • Draft handling: Create, update, and manage email drafts.
  • Calendar integration: Manage calendars and events (currently in development).
  • Path-based navigation: Work with folders using human-readable paths.
  • HTML conversion: Convert HTML emails to readable plain text.

Use cases of MCP Outlook?

  1. Automating email management tasks for users.
  2. Integrating Outlook functionalities into AI applications.
  3. Streamlining calendar event management through AI.

FAQ from MCP Outlook?

  • Can MCP Outlook handle all Outlook functionalities?

Currently, it supports mail, drafts, and folder management, with calendar integration in progress.

  • Is MCP Outlook free to use?

Yes! MCP Outlook is open-source and free to use.

  • What are the prerequisites for using MCP Outlook?

You need Node.js, npm or yarn, a Microsoft Exchange Online account, and an Azure AD application with proper permissions.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
asirulnik
Star
3
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago