How to connect an Outlook MCP with Claude Code (4 steps)

Developers miss a lot of operationally relevant context because it lives in Outlook instead of their terminal.

Outage alerts routed to a shared inbox, vendor API deprecation notices, escalation emails from support, meeting invites for the incident review, all of it sits in Outlook and none of it is visible to Claude Code by default. Getting it into a session means tabbing over to Outlook, searching manually, and copying the relevant parts back into your terminal.

To help your developers access email and calendar data from Outlook without leaving the terminal, we'll show you how to connect Outlook with Merge Agent Handler's Outlook MCP server.

How it works

Merge Agent Handler sits between Claude Code and Microsoft Graph's Outlook API.

You install the Merge CLI, authenticate once with your Merge Agent Handler account, and register the connection with a single command.

Agent Handler also manages OAuth token storage and refresh for your Microsoft 365 account, so you never store or rotate that credential locally.

Related: A guide to integrating Cursor with an Outlook MCP

Prerequisites

Before getting started, you'll need the following:

• A Merge Agent Handler account
• Claude Code installed (run claude --version to confirm)
• pipx installed (run pipx --version to confirm, or install via pip install pipx)
• A Microsoft 365 or Outlook.com account with access to the mailbox and calendar you want to connect

If you want to connect Merge Agent Handler's Outlook MCP with internal or customer-facing agentic products, you can follow the steps in our docs.

1. Install the Merge CLI

Install with pipx: pipx install merge-api

Verify your installation: merge --version

2. Configure the CLI and log in

Run merge login to connect the CLI to your Merge account: merge login

This starts an authenticated session so the CLI can make requests on your behalf.

3. Add Agent Handler to Claude Code

The simplest way to register Agent Handler with Claude Code:

merge setup claude-code

4. Authenticate Outlook

To confirm the connection is working, open a Claude Code session and try: "Find any emails from the last week about the payments API outage, summarize what was reported, and check if any calendar events overlap with the outage window."

The first time you invoke an Outlook tool, a Magic Link will appear to complete connector authentication.

Find any emails from the last week about the payments API outage, summarize what was reported, and check if any calendar events overlap with the outage window.

{{this-blog-only-cta}}

Outlook MCP FAQ

In case you have more questions on setting up and using the Outlook MCP in Claude Code, we've addressed several more commonly-asked questions below.

What can you do once the Outlook MCP is connected to Claude Code?

With Outlook connected, Claude Code can:

• Search messages by keyword, sender, or date: find emails about a specific incident, vendor notice, or customer escalation without leaving the terminal

• Read message content and attachments: have Claude summarize a thread, extract error codes, or pull details out of an attached log file

• List folders and mailbox structure: browse how a shared or personal mailbox is organized so you can scope a search to the right folder

• Draft and send email: compose replies or new messages directly from a Claude Code session

• Query calendar events and availability: check what's on the calendar for a given day or whether attendees are free during a proposed window

• Cross-reference mail and calendar together: confirm whether an alert email lines up with a deployment or meeting that was already scheduled

Why use Merge Agent Handler vs. a self-hosted Outlook MCP server?

You can self-host an MCP server that wraps Microsoft Graph's mail and calendar APIs directly. For a solo developer connecting their own mailbox, that's a workable setup: register an app in Azure AD, request the Graph scopes you need, and manage the token yourself.

It gets harder at team scale.

Microsoft Graph app registrations typically need tenant admin consent, and each developer who wants Outlook access either shares that registration or goes through the same admin approval separately. Token refresh, revocation, and scoping which folders or calendars an agent can reach all become manual problems with no central record of what an agent read or sent.

Merge Agent Handler centralizes the Microsoft Graph connection, handles token storage and refresh, and lets you scope exactly which Outlook operations each agent can call.

Each developer gets isolated credentials under their own Registered User, so revoking one person's access doesn't touch anyone else's setup, and every tool call is logged.

Why connect Outlook to Claude Code?

Outlook holds context that developers need but rarely have in front of them while they're working: customer escalations, vendor deprecation notices, incident retros scheduled on the calendar, and deployment windows booked as meetings.

None of that is visible to Claude Code by default, so developers either reconstruct it from memory or stop what they're doing to go check.

With the Outlook MCP connected, Claude Code can pull that context on demand. You can ask it to find every email mentioning a specific API endpoint, check whether a deployment window is clear on the calendar, or summarize a support thread before starting a debugging session, all without leaving the terminal.

Can I use Merge Agent Handler's Outlook MCP with my employees?

Yes, Agent Handler for Workforce is built to help organizations provision, secure, and govern how employees connect AI to systems like Outlook.

Common patterns include:

• Provisioning and access control via SCIM with identity providers like Okta and Microsoft Entra ID, so IT can manage which mailboxes and calendars an employee's agent can reach by role or team

• DLP and policy enforcement on tool calls, so admins can block queries that would return sensitive email content or attachments before results reach the employee's AI session

• User-level audit logging so security and IT teams can review which messages were read or sent, and which calendar events were viewed or created, by which employee identity, and when

Put together, employees can use the Outlook MCP to search and summarize email threads, check calendar availability, and cross-reference schedule and inbox context, and more, while IT keeps centralized control over which mailboxes and calendars each identity can reach.