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-calendar 'https://gateway.pipeworx.io/outlook-calendar/mcp'{
"mcpServers": {
"outlook-calendar": {
"type": "http",
"url": "https://gateway.pipeworx.io/outlook-calendar/mcp"
}
}
}@pipeworx/mcp-outlook-calendarclaude mcp add outlook-calendar -e 'PIPEWORX_API_KEY=<your pipeworx_api_key>' -- npx -y @pipeworx/mcp-outlook-calendar@0.2.0{
"mcpServers": {
"outlook-calendar": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-outlook-calendar@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-calendar
Outlook Calendar MCP Pack
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
Tools
| Tool | Description |
|---|---|
list_events | List upcoming events from the user's Outlook / Microsoft 365 calendar within a time window. Returns subject, start/end times, location, organizer, all-day flag, and online meeting URL for each event. Defaults to the next 7 days. Use to see what meetings or appointments are scheduled. |
get_event | Get full details of a single Outlook / Microsoft 365 calendar event by its ID. Returns subject, start/end times, location, organizer, attendees, body, all-day flag, and online meeting URL. Use after list_events to inspect a specific meeting. |
list_calendars | List all calendars accessible in the user's Outlook / Microsoft 365 account. Returns each calendar's ID, name, owner, edit permission, and whether it is the default calendar. Use to discover which calendars exist. |
find_meeting_times | Return the user's busy time windows from their Outlook / Microsoft 365 calendar over the next N days — a lightweight free/busy view. Each window includes start, end, subject, and all-day flag. Use to find when the user is available or to identify scheduling conflicts before proposing a meeting time. |
get_profile | Get the signed-in user's Microsoft 365 / Outlook profile: display name, primary email (mail), and user principal name. Use to confirm whose calendar is connected. |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"outlook-calendar": {
"url": "https://gateway.pipeworx.io/outlook-calendar/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/outlook-calendar/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/list_events with Authorization: Bearer <your Pipeworx key>. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/list_events. 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-calendar": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-outlook-calendar"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-outlook-calendarIt 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 Calendar data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Frequently asked questions
What is Outlook Calendar?
Outlook Calendar MCP Pack
How do I install Outlook Calendar?
It runs as a remote server. In Claude Code: claude mcp add --transport http outlook-calendar 'https://gateway.pipeworx.io/outlook-calendar/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Outlook Calendar need an API key?
Yes. It expects PIPEWORX_API_KEY, which you set in its configuration.
Is Outlook Calendar open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains Outlook Calendar?
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.