Microsoft 365 MCP Server

Authenticate with Microsoft using device code flow

Log out from Microsoft account

Check current Microsoft authentication status

List all available Microsoft accounts

Select a specific Microsoft account to use

Remove a Microsoft account from the cache

Delete navigation property items for drives

Return a collection of DriveItems in the children relationship of a DriveItem. DriveItems with a non-null folder or package facet can have one or more child DriveItems.

The content stream, if the item represents a file.

The content stream, if the item represents a file.

Represents a collection of worksheets associated with the workbook. Read-only.

Creates a new chart.

Update the navigation property format in drives

Update the navigation property sort in drives

Invoke function range

The root folder of the drive. Read-only.

Retrieve the properties and relationships of user object. This operation returns by default only a subset of the more commonly used properties for each user. These default properties are noted in the Properties section. To get properties that are not returned by default, do a GET operation for the user and specify the properties in a $select OData query option. Because the user resource supports extensions, you can also use the GET operation to get custom properties and extension data in a user instance. Customers through Microsoft Entra ID for customers can also use this API operation to retrieve their details.

Get all the user's calendars (/calendars navigation property), get the calendars from the default calendar group or from a specific calendar group.

The calendar view for the calendar. Navigation property. Read-only.

💡 TIP: Returns expanded recurring event instances (not just seriesMaster) within a date range for a specific calendar. Requires startDateTime and endDateTime query parameters in ISO 8601 format (e.g., 2024-01-01T00:00:00Z). Each instance includes seriesMasterId and type (occurrence/exception) fields for recurring event linkage. Use fetchAllPages=true to retrieve all results when there are many events.

The events in the calendar. Navigation property. Read-only.

Use this API to create a new event in a calendar. The calendar can be one for a user, or the default calendar of a Microsoft 365 group.

💡 TIP: CRITICAL: Do not try to guess the email address of the recipients. Use the list-users tool to find the email address of the recipients.

The events in the calendar. Navigation property. Read-only.

Update the navigation property events in me

💡 TIP: CRITICAL: Do not try to guess the email address of the recipients. Use the list-users tool to find the email address of the recipients.

Delete navigation property events for me

The occurrences of a recurring series, if the event is a series master. This property includes occurrences that are part of the recurrence pattern, and exceptions modified, but doesn't include occurrences canceled from the series. Navigation property. Read-only. Nullable.

💡 TIP: Expand a recurring event into individual instances within a date range. Requires startDateTime and endDateTime query parameters in ISO 8601 format (e.g., 2024-01-01T00:00:00Z). Use this to see all occurrences of a recurring event.

Get the occurrences, exceptions, and single instances of events in a calendar view defined by a time range, from the user's default calendar, or from some other calendar of the user.

💡 TIP: Returns expanded recurring event instances (not just seriesMaster) within a date range for the default calendar. Requires startDateTime and endDateTime query parameters in ISO 8601 format (e.g., 2024-01-01T00:00:00Z). Use get-specific-calendar-view if you need a non-default calendar.

Get a contact collection from the default contacts folder of the signed-in user. There are two scenarios where an app can get contacts in another user's contact folder:

Add a contact to the root Contacts folder or to the contacts endpoint of another contact folder.

Retrieve the properties and relationships of a contact object. There are two scenarios where an app can get a contact in another user's contact folder:

Update the properties of a contact object.

Delete a contact.

Retrieve the list of Drive resources available for a target User, Group, or Site.

Get a list of event objects in the user's mailbox. The list contains single instance meetings and series masters. To get expanded event instances, you can get the calendar view, or get the instances of an event. Currently, this operation returns event bodies in only HTML format. There are two scenarios where an app can get events in another user's calendar:

Create one or more multi-value extended properties in a new or existing instance of a resource. The following user resources are supported: The following group resources are supported: See Extended properties overview for more information about when to use open extensions or extended properties, and how to specify extended properties.

💡 TIP: CRITICAL: Do not try to guess the email address of the recipients. Use the list-users tool to find the email address of the recipients.

Get the properties and relationships of the specified event object. Currently, this operation returns event bodies in only HTML format. There are two scenarios where an app can get an event in another user's calendar: Since the event resource supports extensions, you can also use the GET operation to get custom properties and extension data in an event instance.

Update the properties of the event object.

💡 TIP: CRITICAL: Do not try to guess the email address of the recipients. Use the list-users tool to find the email address of the recipients.

Removes the specified event from the containing calendar. If the event is a meeting, deleting the event on the organizer's calendar sends a cancellation message to the meeting attendees.

Get the mail folder collection directly under the root folder of the signed-in user. The returned collection includes any mail search folders directly under the root. By default, this operation does not return hidden folders. Use a query parameter includeHiddenFolders to include them in the response. This operation does not return all mail folders in a mailbox, only the child folders of the root folder. To return all mail folders in a mailbox, each child folder must be traversed separately.

Get the folder collection under the specified folder. You can use the .../me/mailFolders shortcut to get the top-level folder collection and navigate to another folder. By default, this operation does not return hidden folders. Use a query parameter includeHiddenFolders to include them in the response.

Get all the messages in the specified user's mailbox, or those messages in a specified folder in the mailbox.

💡 TIP: CRITICAL: When searching emails, the $search parameter value MUST be wrapped in double quotes. Format: $search="your search query here". Use KQL (Keyword Query Language) syntax to search specific properties: 'from:', 'subject:', 'body:', 'to:', 'cc:', 'bcc:', 'attachment:', 'hasAttachments:', 'importance:', 'received:', 'sent:'. Examples: $search="from:john@example.com" | $search="subject:meeting AND hasAttachments:true" | $search="body:urgent AND received>=2024-01-01" | $search="from:alice AND importance:high". Remember: ALWAYS wrap the entire search expression in double quotes! Reference: https://learn.microsoft.com/en-us/graph/search-query-parameter

Get an open extension (openTypeExtension object) identified by name or fully qualified name. The table in the Permissions section lists the resources that support open extensions. The following table lists the three scenarios where you can get an open extension from a supported resource instance.

💡 TIP: CRITICAL: When searching emails, the $search parameter value MUST be wrapped in double quotes. Format: $search="your search query here". Use KQL (Keyword Query Language) syntax to search specific properties: 'from:', 'subject:', 'body:', 'to:', 'cc:', 'bcc:', 'attachment:', 'hasAttachments:', 'importance:', 'received:', 'sent:'. Examples: $search="from:john@example.com" | $search="subject:meeting AND hasAttachments:true" | $search="body:urgent AND received>=2024-01-01" | $search="from:john AND importance:high". Remember: ALWAYS wrap the entire search expression in double quotes! Reference: https://learn.microsoft.com/en-us/graph/search-query-parameter

Create an open extension (openTypeExtension object) and add custom properties in a new or existing instance of a resource. You can create an open extension in a resource instance and store custom data to it all in the same operation, except for specific resources. The table in the Permissions section lists the resources that support open extensions.

Get the properties and relationships of the eventMessage object. Apply the $expand parameter on the event navigation property to get the associated event in an attendee's calendar. Currently, this operation returns event message bodies in only HTML format.

Update the properties of an eventMessage object.

Delete eventMessage.

Retrieve a list of attachment objects.

Use this API to create a new Attachment. An attachment can be one of the following types: All these types of attachment resources are derived from the attachment resource.

Read the properties, relationships, or raw contents of an attachment that is attached to a user event, message, or group post. An attachment can be one of the following types: All these types of attachments are derived from the attachment resource.

Delete navigation property attachments for me

Create a draft to forward an existing message, in either JSON or MIME format. When using JSON format, you can:

• Specify either a comment or the body property of the message parameter. Specifying both will return an HTTP 400 Bad Request error.

• Specify either the toRecipients parameter or the toRecipients property of the message parameter. Specifying both or specifying neither will return an HTTP 400 Bad Request error.

• Update the draft later to add content to the body or change other message properties. When using MIME format:

• Provide the applicable Internet message headers and the MIME content, all encoded in base64 format in the request body.

• Add any attachments and S/MIME properties to the MIME content. Send the draft message in a subsequent operation. Alternatively, forward a message in a single operation.

💡 TIP: Create a forward draft (does not send). Useful when user wants to review before sending.

Create a draft to reply to the sender of a message in either JSON or MIME format. When using JSON format:

• Specify either a comment or the body property of the message parameter. Specifying both will return an HTTP 400 Bad Request error.

• If replyTo is specified in the original message, per Internet Message Format (RFC 2822), you should send the reply to the recipients in replyTo, and not the recipients in from.

• You can update the draft later to add reply content to the body or change other message properties. When using MIME format:

• Provide the applicable Internet message headers and the MIME content, all encoded in base64 format in the request body.

• Add any attachments and S/MIME properties to the MIME content. Send the draft message in a subsequent operation. Alternatively, reply to a message in a single operation.

Create a draft to reply to the sender and all recipients of a message in either JSON or MIME format. When using JSON format:

• Specify either a comment or the body property of the message parameter. Specifying both will return an HTTP 400 Bad Request error.

• If the original message specifies a recipient in the replyTo property, per Internet Message Format (RFC 2822), you should send the reply to the recipients in the replyTo and toRecipients properties, and not the recipients in the from and toRecipients properties.

• You can update the draft later to add reply content to the body or change other message properties. When using MIME format:

• Provide the applicable Internet message headers and the MIME content, all encoded in base64 format in the request body.

• Add any attachments and S/MIME properties to the MIME content. Send the draft message in a subsequent operation. Alternatively, reply-all to a message in a single action.

Forward a message using either JSON or MIME format. When using JSON format, you can:

• Specify either a comment or the body property of the message parameter. Specifying both will return an HTTP 400 Bad Request error.

• Specify either the toRecipients parameter or the toRecipients property of the message parameter. Specifying both or specifying neither will return an HTTP 400 Bad Request error. When using MIME format:

• Provide the applicable Internet message headers and the MIME content, all encoded in base64 format in the request body.

• Add any attachments and S/MIME properties to the MIME content. This method saves the message in the Sent Items folder. Alternatively, create a draft to forward a message, and send it later.

💡 TIP: Forward an email preserving full HTML formatting and attachments. The 'comment' field adds text above the forwarded content. toRecipients is required. Do NOT reconstruct the email manually - this endpoint handles everything server-side.

Move a message to another folder within the specified user's mailbox. This creates a new copy of the message in the destination folder and removes the original message.

Reply to the sender of a message using either JSON or MIME format. When using JSON format:

• Specify either a comment or the body property of the message parameter. Specifying both will return an HTTP 400 Bad Request error.

• If the original message specifies a recipient in the replyTo property, per Internet Message Format (RFC 2822), send the reply to the recipients in replyTo and not the recipient in the from property. When using MIME format:

• Provide the applicable Internet message headers and the MIME content, all encoded in base64 format in the request body.

• Add any attachments and S/MIME properties to the MIME content. This method saves the message in the Sent Items folder. Alternatively, create a draft to reply to an existing message and send it later.

💡 TIP: Reply to an email preserving full HTML formatting. The 'comment' field is your reply text. Do NOT reconstruct the email manually.

Reply to all recipients of a message using either JSON or MIME format. When using JSON format:

• Specify either a comment or the body property of the message parameter. Specifying both will return an HTTP 400 Bad Request error.

• If the original message specifies a recipient in the replyTo property, per Internet Message Format (RFC 2822), send the reply to the recipients in replyTo and not the recipient in the from property. When using MIME format:

• Provide the applicable Internet message headers and the MIME content, all encoded in base64 format in the request body.

• Add any attachments and S/MIME properties to the MIME content. This method saves the message in the Sent Items folder. Alternatively, create a draft to reply-all to a message and send it later.

💡 TIP: Reply-all preserving full HTML formatting. The 'comment' field is your reply text.

Send an existing draft message. The draft message can be a new message draft, reply draft, reply-all draft, or a forward draft. This method saves the message in the Sent Items folder. Alternatively, send a new message in a single operation.

Retrieve a list of notebook objects.

Retrieve a list of onenoteSection objects from the specified notebook.

Create a new OneNote page in the default section of the default notebook. To create a page in a different section in the default notebook, you can use the sectionName query parameter. Example: ../onenote/pages?sectionName=My%20section The POST /onenote/pages operation is used only to create pages in the current user's default notebook. If you're targeting other notebooks, you can create pages in a specified section.

The page's HTML content.

Retrieve a list of page objects from the specified section.

Create a new page in the specified section.

Retrieve a list of plannertask objects assigned to a User.

Send the message specified in the request body using either JSON or MIME format. When using JSON format, you can include a file attachment in the same sendMail action call. When using MIME format: This method saves the message in the Sent Items folder. Alternatively, create a draft message to send later. To learn more about the steps involved in the backend before a mail is delivered to recipients, see here.

💡 TIP: CRITICAL: Do not try to guess the email address of the recipients. Use the list-users tool to find the email address of the recipients.

Get a list of the todoTaskList objects and their properties.

Get the todoTask resources from the tasks navigation property of a specified todoTaskList.

Create a new task object in a specified todoTaskList.

Read the properties and relationships of a todoTask object.

Update the properties of a todoTask object.

Delete a todoTask object.

Retrieve the properties and relationships of a plannerplan object.

Retrieve a list of plannerTask objects associated with a plannerPlan object.

Create a new plannerTask.

Retrieve the properties and relationships of plannerTask object.

Update the properties of plannerTask object.

Update the properties of plannerTaskDetails object.

Runs the query specified in the request body. Search results are provided in the response.