Sign in Book a demo
Back to Tools
Productivity & Docs OAuth
Build Your Agent View Documentation
microsoft-outlook-calendar logo

Microsoft Outlook Calendar MCP Tools for AI Agents

Let an agent check availability, search events, inspect calendars, and create meetings in Outlook Calendar.

Available Tools

15 tools available in this integration

MicrosoftOutlookCalendar.CancelEvent

Cancel a meeting you organize and email a cancellation to every invitee.

MicrosoftOutlookCalendar.CreateEvent

Create an event in the user's default calendar, or in another calendar they can edit

MicrosoftOutlookCalendar.FindMeetingTimes

Propose times when a group could meet.

MicrosoftOutlookCalendar.ForwardEvent

Send a meeting invitation to someone who is not invited yet; they join the attendee list and the organizer is told.

MicrosoftOutlookCalendar.GetEvent

Get one event from any of the user's calendars, with the calendar it is on.

MicrosoftOutlookCalendar.GetSchedule

Get free/busy and calendar items in a time window for one or more people.

MicrosoftOutlookCalendar.ListCalendars

List all calendars the user has access to.

MicrosoftOutlookCalendar.ListEventAttachments

List attachment metadata for a calendar event.

MicrosoftOutlookCalendar.ListEventInstances

List the dates one recurring series falls on between two times.

MicrosoftOutlookCalendar.ListEventsInTimeRange

List everything on the user's calendars between two times.

MicrosoftOutlookCalendar.RemoveEventFromMyCalendar

Take an event off your calendar without emailing anyone.

MicrosoftOutlookCalendar.RespondToEvent

Accept, decline or tentatively accept a meeting someone else invited you to, and tell the organizer.

MicrosoftOutlookCalendar.SearchEvents

Find calendar events by what is true about them: subject text, who attends,

MicrosoftOutlookCalendar.UpdateEvent

Change one event in the user's calendar, in place.

MicrosoftOutlookCalendar.WhoAmI

Get information about the current user and their Outlook Calendar environment.

Why agent-optimized tools matter

Built for intent, not API schemas

Ask the agent to "find a 45-minute time next week with the product team and send an invite after I approve it." Arcade picks the right Outlook Calendar actions without guessing calendar IDs or event IDs.

Up to 100x fewer tokens

Outlook Calendar list and search reads return focused event and schedule details, while recurring instances and attachment metadata are fetched only when needed, so the agent can plan without loading every calendar into the model.

Complete the workflow end to end

Check availability, propose a meeting time, create the invitation, update attendees, and cancel or respond to events through one toolkit designed around the complete calendar task.

Make actions predictable and controlled

Arcade tools return structured results and useful errors across users and runs. Teams can apply scope restrictions, redaction, and approval policies so agents follow the same controls every time.

Securing Microsoft Outlook Calendar

The more capabilities agents get, the more useful they are. However, more capabilities bring more risks of undesired effects such as data loss and exfiltration.

This is why Arcade provides you with contextual rules that dictate how and when a tool is allowed to run. Arcade’s contextual access lets you govern tool visibility and behavior at every stage of execution and control who can see a tool, what inputs are allowed, and what comes back.

Learn about Contextual Access Policies

For Microsoft Outlook Calendar, you can implement some of these policies:

Access when tools are listed for a user
  • Hide MicrosoftOutlookCalendar.CancelEvent from agents unless the roles your IDP marks as calendar owners are active, so an agent cannot cancel meetings organized by someone else.
  • Restrict MicrosoftOutlookCalendar.RemoveEventFromMyCalendar to agents acting for the calendar owner, so a shared-calendar workflow cannot silently remove another user's event from their calendar.
  • Deny MicrosoftOutlookCalendar.ForwardEvent to agents outside your meeting-coordinator role, so an agent cannot add external attendees to internal meetings without the right authority.
Pre-execution before each tool call
  • Require human approval before MicrosoftOutlookCalendar.CreateEvent runs when the event includes external attendees, so an agent cannot send an unsolicited invitation outside your organization.
  • Block MicrosoftOutlookCalendar.UpdateEvent when it changes the time, location, or attendee list of an event marked confidential, so an agent cannot alter a sensitive meeting without review.
  • Require human approval before MicrosoftOutlookCalendar.RespondToEvent sends an acceptance or decline for meetings with external organizers, so an agent cannot commit the user to or withdraw them from a consequential meeting.
Post-execution after the tool returns
  • Redact MicrosoftOutlookCalendar.GetEvent results' attendee email addresses, private notes, and meeting-body content before they reach the model, so calendar lookups do not expose personal or confidential details.
  • Strip meeting subjects, locations, and attendee names from MicrosoftOutlookCalendar.GetSchedule results, leaving only availability windows so the model cannot infer private appointments.
  • Deny MicrosoftOutlookCalendar.ListEventAttachments results for events marked confidential, so an agent cannot discover the names of files attached to sensitive meetings.

How to use Microsoft Outlook Calendar with your agent

Connect your MCP client and follow the setup from authorization through your first calendar request. Then give your agent prompts for finding open times, checking events, or creating a meeting.

Your questions, answered

A Microsoft Outlook Calendar MCP server exposes calendar capabilities as structured tools that an AI agent can call through the Model Context Protocol. After a user authorizes their Microsoft account, the agent can check availability, find meeting times, create or update events, and respond to invitations.

Arcade provides an independent MCP endpoint for Outlook Calendar and adds user-level OAuth, agent-optimized actions, approval workflows, redaction, and scope controls. That gives teams one governed way to connect calendar actions from different agents and clients.

Arcade agents can list calendars and events, search for meetings, inspect recurring instances and attachment metadata, check free/busy schedules, propose meeting times, create and update events, forward invitations, respond to meetings, remove events from the user's calendar, and cancel meetings they organize with notifications to invitees.

Arcade requests the Microsoft Graph calendar permissions required by the actions you enable. Read-only workflows generally need calendar read access, while creating, updating, responding to, forwarding, removing, or canceling events requires calendar write access; shared-calendar and schedule checks may require shared-calendar permissions. Grant the narrowest permissions that support the workflow.

Yes. Each user authorizes their own Microsoft account through OAuth. Calendar actions run under that user's authorization, so the agent can access only the calendars and permissions that person has approved.

Yes. Contextual Access policies can require human approval before consequential actions such as sending an invitation, changing an event, declining a meeting, or canceling a meeting for all invitees. The call proceeds only after the policy's conditions have been satisfied.

Arcade proxies Microsoft Graph calendar calls and does not persist your calendar content as part of normal tool execution. OAuth credentials are brokered and stored encrypted at rest, and the model never receives raw credentials.

Any framework or client that can connect to Arcade's MCP gateway or tool APIs works, including LangChain, OpenAI Agents, CrewAI, Claude Desktop, Claude Code, Cursor, Visual Studio Code, Microsoft Copilot Studio, and GitHub Copilot.

Arcade refreshes access while the user's Microsoft authorization remains valid. If access is revoked, rotated, or can no longer be refreshed, calendar actions stop until the user reconnects their account.

Microsoft Graph throttling, tenant policies, mailbox limits, and account-level calendar restrictions still apply to actions performed through Arcade. Large time-range searches, schedule checks across many people, and high-volume event changes may be throttled or limited by Microsoft.

Ready to actually ship your agent?

Connect your agent to Microsoft Outlook Calendar with managed OAuth, agent-optimized tools and approval controls for consequential actions.

Build Your Agent Read the Microsoft Outlook Calendar Quickstart