Mcp Outlook

Created By
sssSofiaSa year ago
A lightweight MCP Server for seamless integration with Microsoft Outlook, enabling MCP clients to interact with emails for specific users. Developed by sofias tech. This server provides a clean interface to Outlook email resources through the Model Context Protocol (MCP), with operations for reading, searching, creating, updating, and deleting emails.
Overview

What is Mcp Outlook?

Mcp Outlook is a lightweight MCP Server designed for seamless integration with Microsoft Outlook, allowing MCP clients to interact with emails for specific users. It provides a clean interface to Outlook email resources through the Model Context Protocol (MCP).

How to use Mcp Outlook?

To use Mcp Outlook, set up the server by registering an app in Azure AD, configuring the necessary permissions, and running the server with the required environment variables. You can then interact with the server using various tools to manage emails.

Key features of Mcp Outlook?

  • Retrieve specific emails by ID.
  • Search emails using OData filter syntax.
  • Create, update, and delete emails.
  • Download emails within a specific date range.

Use cases of Mcp Outlook?

  1. Automating email management tasks for users.
  2. Integrating email functionalities into other applications.
  3. Providing a backend service for email-related operations in custom software.

FAQ from Mcp Outlook?

  • What permissions are required to use Mcp Outlook?

You need to grant Mail.ReadWrite, Mail.Send, and User.Read permissions in Azure AD.

  • Is Mcp Outlook free to use?

Yes, Mcp Outlook is open-source and free to use under the MIT License.

  • Can I access multiple user mailboxes?

Yes, the server supports accessing multiple user mailboxes through application permissions.

Server Config

{
  "mcpServers": {
    "outlook": {
      "command": "uvx",
      "args": [
        "mcp-outlook"
      ],
      "env": {
        "ID_CLIENT": "your-app-id",
        "APP_SECRET": "your-app-secret",
        "TENANT_ID": "your-tenant-id"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
sssSofiaS
Star
-
Language
-
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