Connect Outlook to Claude Code

Make Claude draft replies in the thread and triage your Outlook inbox. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Outlook to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Outlook, you add a Outlook MCP server: a small hosted service that exposes Outlook's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Outlook account. No API keys pasted into config files.

claude mcp add --transport http outlook https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Outlook once connected?

Full read-write Outlook access lets Claude draft a reply in the original conversation, keep the recipients and quoted history intact, move messages into folders, apply categories, flag for follow-up, and send once you approve. The drafting and triage that used to mean copy-paste happen where the email already lives.

Draft a reply inside an existing conversation, preserving recipients and quoted history
Move messages into folders to triage and clear an inbox
Apply or remove categories and flag messages for follow-up
Mark conversations read or archive them as you process them
Send a drafted message after you approve it
Find every message matching a query and propose batched responses

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Outlook access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Outlook API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Outlook changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Outlook connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Outlook connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Outlook account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Outlook's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Outlook?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Outlook account it signs in with. Revoking access is one click in Outlook.

More on the Outlook connector

Outlook connector for claude.ai Gmail + Claude Code Slack + Claude Code Microsoft Teams + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us