Skip to main content
Glama
@lnwebworks/outlook-mcp-server

@lnwebworks/outlook-mcp-server

by access-ctrl

@lnwebworks/outlook-mcp-server

An MCP (Model Context Protocol) server that connects Claude (or any MCP-compatible client) to Outlook via the Microsoft Graph API, using client-credentials (app-only) auth.

Installation

npm install -g @lnwebworks/outlook-mcp-server

Or run directly with npx:

npx @lnwebworks/outlook-mcp-server

Related MCP server: Outlook MCP Server

Configuration

Copy .env.example to .env and fill in your Azure AD app registration details:

cp .env.example .env

Required:

  • AZURE_TENANT_ID

  • AZURE_CLIENT_ID

  • AZURE_CLIENT_SECRET

  • OUTLOOK_USER_EMAIL — the mailbox this server acts on by default

Optional:

  • OUTLOOK_EXCLUDED_FOLDER_IDS

  • OUTLOOK_SKIP_EXCLUDED_FOLDERS

  • OUTLOOK_SIGNOFF_NAME

Usage with an MCP client

Add this server to your MCP client's config, e.g.:

{
  "mcpServers": {
    "outlook": {
      "command": "npx",
      "args": ["-y", "@lnwebworks/outlook-mcp-server"],
      "env": {
        "AZURE_TENANT_ID": "...",
        "AZURE_CLIENT_ID": "...",
        "AZURE_CLIENT_SECRET": "...",
        "OUTLOOK_USER_EMAIL": "..."
      }
    }
  }
}

License

MIT

Available Tools

22 tools
cancel_calendar_eventA

Cancel a calendar event and notify attendees

Inputs: eventId (required), comment, mailbox.

create_calendar_eventA

Create a new calendar event. Requires approval. Automatically checks for conflicting events in that time range first and refuses (returning conflict:true and the conflicting events) unless force:true is passed — only pass force:true after the user has explicitly approved double-booking.

Inputs: endTime (required), subject (required), startTime (required), body, +5 more.

create_email_draftA

Create a standalone draft email in Outlook Drafts folder for review before sending. Supports file attachments up to 25MB combined.

Inputs: to (required), body (required), subject (required), cc, +4 more.

create_reply_draftA

Create an unsent draft reply attached to an existing email thread using Microsoft Graph createReply API (POST /messages/{id}/createReply). Supports file attachments up to 25MB combined.

Inputs: messageId (required), cc, bcc, body, +3 more.

get_calendar_eventsA

Get calendar events between two datetimes

Inputs: endTime (required), startTime (required), mailbox.

get_conversation_threadB

Retrieve full email conversation history by conversation ID

Inputs: conversationId (required), limit, mailbox.

get_email_attachmentsA

Fetches the content of all the file attachments for a given Outlook messageId. Returns array [{id, name, contentType, size, isInline, contentBytes}].

Inputs: id (required), mailbox.

get_email_foldersA

List all Outlook mail folders with unread counts

Inputs: mailbox.

get_recent_emailsC

Fetch recently received emails from Outlook inbox

Inputs: limit, mailbox.

get_recent_emails_all_foldersA

Fetch recently received emails across the entire mailbox (all folders, not just Inbox), excluding Deleted Items (and its subfolders), Junk, Junk Emails, and Drafts. Returns bodyPreview (short text snippet) instead of full HTML body to keep payload small.

Inputs: limit, mailbox.

get_sent_emailsA

Fetch sent emails to track outbox and detect missing replies

Inputs: limit, mailbox.

get_todays_briefingB

Get today's unread emails and calendar events in one call

Inputs: mailbox.

get_unread_emailsB

Fetch all unread emails from Outlook inbox for triage

Inputs: mailbox.

get_upcoming_eventsC

Get upcoming calendar events for the next N days

Inputs: days, mailbox.

mark_email_readC

Mark an email as read or unread

Inputs: emailId (required), isRead, mailbox.

move_emailC

Move an email to a specific folder

Inputs: emailId (required), destinationFolderId (required), mailbox.

reply_to_emailA

Reply to an existing email thread. Requires prior approval. Supports file attachments up to 25MB combined (over 3MB sends via an internal draft-then-send step — same result, no different usage).

Inputs: body (required), emailId (required), cc, bcc, +3 more.

search_emailsB

Search emails by keyword, sender, subject or topic

Inputs: query (required), limit, mailbox.

send_emailA

Send an approved email. Requires explicit approval from the client first. Supports file attachments up to 25MB combined (over 3MB sends via an internal draft-then-send step — same result, no different usage).

Inputs: to (required), body (required), subject (required), cc, +3 more.

triage_emailC

Classify an email for urgency, category and suggest a reply

Inputs: id (required), body (required), sender (required), subject (required), +1 more.

update_calendar_eventA

Update an existing calendar event. If both startTime and endTime are being changed, automatically checks for conflicting events in the new time range first and refuses (returning conflict:true and the conflicting events) unless force:true is passed — only pass force:true after the user has explicitly approved double-booking.

Inputs: eventId (required), body, force, endTime, +5 more.

update_email_draftA

Update/edit an existing email draft subject, body, or recipient before sending (PATCH /messages/{draftId})

Inputs: draftId (required), cc, to, bcc, +3 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 22 tools

    Disambiguation3/5

    There is a cluster of email retrieval tools—get_recent_emails, get_recent_emails_all_folders, get_unread_emails, and get_todays_briefing—that overlap in function and could lead an agent to pick the wrong one by name alone. Most other tools are clearly separated by resource/action, and the descriptions resolve the ambiguity if read carefully.

    Naming Consistency5/5

    All tools use snake_case verb_noun names (get_, create_, update_, cancel_, send_, reply_to_, move_, mark_) with no camelCase or inconsistent style. Even phrase-based names like get_todays_briefing still follow the get_<thing> convention, so the pattern is predictable.

    Tool Count3/5

    22 tools is on the heavy side for a mail/calendar server, and the four overlapping email-fetch variants add redundancy rather than distinct capabilities. A tighter set closer to 15-16 tools would be easier to navigate, though the count is not extreme.

    Completeness4/5

    Email covers fetch, search, triage, drafts, replies, send, move, mark-read, and attachments; calendar covers create/read/update/cancel with conflict checks. The main gaps are no email deletion or forwarding and no direct send for an existing draft, but agents can work around these.

    Related MCP Connectors

    Related MCP Servers