Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http outlook-mail 'https://gateway.pipeworx.io/outlook-mail/mcp'{
"mcpServers": {
"outlook-mail": {
"type": "http",
"url": "https://gateway.pipeworx.io/outlook-mail/mcp"
}
}
}@pipeworx/mcp-outlook-mailclaude mcp add outlook-mail -e 'PIPEWORX_API_KEY=<your pipeworx_api_key>' -- npx -y @pipeworx/mcp-outlook-mail@0.2.0{
"mcpServers": {
"outlook-mail": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-outlook-mail@0.2.0"
],
"env": {
"PIPEWORX_API_KEY": "<your pipeworx_api_key>"
}
}
}
}Environment variables
PIPEWORX_API_KEYsecret Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
mcp-outlook-mail
Outlook Mail (Microsoft 365) MCP Pack
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
Tools
| Tool | Description |
|---|---|
outlook_list_messages | List email messages from an Outlook / Microsoft 365 mailbox folder (default: inbox). Returns compact message summaries (subject, sender, received time, preview, read status, attachment flag). Supports keyword search and unread-only filtering. Use to browse a user's Outlook email. |
outlook_get_message | Get the full content of a single Outlook / Microsoft 365 email message by its ID, including subject, sender, recipients (to/cc), received time, and the full body (HTML or text). Use after outlook_list_messages or outlook_search_messages to read an email in full. |
outlook_list_folders | List the mail folders in an Outlook / Microsoft 365 mailbox, with display names, unread counts, and total item counts. Use to discover folder names/IDs before listing messages. |
outlook_search_messages | Search across an entire Outlook / Microsoft 365 mailbox by keyword. Returns matching email summaries (subject, sender, received time, preview). Use to find emails by topic, sender, or content regardless of folder. |
outlook_get_profile | Get the signed-in user's Microsoft 365 / Outlook profile: display name, email address, user principal name, job title, and mobile phone. Use to identify whose mailbox is connected. |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"outlook-mail": {
"url": "https://gateway.pipeworx.io/outlook-mail/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/outlook-mail/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1683+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
This pack runs against a connected microsoft account, so it needs a Pipeworx key: sign in at https://pipeworx.io/account, connect microsoft, then call POST https://gateway.pipeworx.io/v1/tools/outlook_list_messages with Authorization: Bearer <your Pipeworx key>. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/outlook_list_messages. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"outlook-mail": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-outlook-mail"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-outlook-mailIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Outlook Mail data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Frequently asked questions
What is Outlook Mail?
Outlook Mail (Microsoft 365) MCP Pack
How do I install Outlook Mail?
It runs as a remote server. In Claude Code: claude mcp add --transport http outlook-mail 'https://gateway.pipeworx.io/outlook-mail/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Outlook Mail need an API key?
Yes. It expects PIPEWORX_API_KEY, which you set in its configuration.
Is Outlook Mail open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains Outlook Mail?
It is published by pipeworx-io. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.