@softeria/ms-365-mcp-server 0.31.1 → 0.32.0

package/dist/endpoints.json

@@ -84,6 +84,12 @@
     "toolName": "move-mail-message",
     "scopes": ["Mail.ReadWrite"]
   },
+  {
+    "pathPattern": "/me/messages/{message-id}",
+    "method": "patch",
+    "toolName": "update-mail-message",
+    "scopes": ["Mail.ReadWrite"]
+  },
   {
     "pathPattern": "/me/messages/{message-id}/attachments",
     "method": "post",
@@ -295,8 +301,7 @@
     "pathPattern": "/me/onenote/pages/{onenotePage-id}/content",
     "method": "get",
     "toolName": "get-onenote-page-content",
-    "scopes": ["Notes.Read"],
-    "returnDownloadUrl": true
+    "scopes": ["Notes.Read"]
   },
   {
     "pathPattern": "/me/onenote/pages",

package/dist/generated/client.js

@@ -5174,6 +5174,64 @@ Based on this value, you can better adjust the parameters and call findMeetingTi
     ],
     response: z.void()
   },
+  {
+    method: "patch",
+    path: "/me/messages/:messageId",
+    alias: "update-mail-message",
+    description: `Update the properties of an eventMessage object.`,
+    requestFormat: "json",
+    parameters: [
+      {
+        name: "body",
+        description: `New navigation property values`,
+        type: "Body",
+        schema: z.object({
+          id: z.string().describe("The unique identifier for an entity. Read-only.").optional(),
+          createdDateTime: z.string().regex(
+            /^[0-9]{4,}-(0[1-9]|1[012])-(0[1-9]|[12][0-9]|3[01])T([01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9]([.][0-9]{1,12})?(Z|[+-][0-9][0-9]:[0-9][0-9])$/
+          ).datetime({ offset: true }).describe(
+            "The Timestamp type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z"
+          ).nullish(),
+          lastModifiedDateTime: z.string().regex(
+            /^[0-9]{4,}-(0[1-9]|1[012])-(0[1-9]|[12][0-9]|3[01])T([01][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9]([.][0-9]{1,12})?(Z|[+-][0-9][0-9]:[0-9][0-9])$/
+          ).datetime({ offset: true }).describe(
+            "The Timestamp type represents date and time information using ISO 8601 format and is always in UTC time. For example, midnight UTC on Jan 1, 2014 is 2014-01-01T00:00:00Z"
+          ).nullish(),
+          body: microsoft_graph_itemBody.optional(),
+          subject: z.string().describe("The subject of the message.").nullish(),
+          attachments: z.array(microsoft_graph_attachment).describe("The fileAttachment and itemAttachment attachments for the message.").optional(),
+          categories: z.array(z.string().nullable()).describe("The categories associated with the item").optional(),
+          changeKey: z.string().describe(
+            "Identifies the version of the item. Every time the item is changed, changeKey changes as well. This allows Exchange to apply changes to the correct version of the object. Read-only."
+          ).nullish(),
+          bccRecipients: z.array(microsoft_graph_recipient).describe("The Bcc: recipients for the message.").optional(),
+          bodyPreview: z.string().describe("The first 255 characters of the message body. It is in text format.").nullish(),
+          ccRecipients: z.array(microsoft_graph_recipient).describe("The Cc: recipients for the message.").optional(),
+          conversationId: z.string().describe("The ID of the conversation the email belongs to.").nullish(),
+          conversationIndex: z.string().describe("Indicates the position of the message within the conversation.").nullish(),
+          flag: microsoft_graph_followupFlag.optional(),
+          from: microsoft_graph_recipient.optional(),
+          hasAttachments: z.boolean().describe(
+            "Indicates whether the message has attachments. This property doesn't include inline attachments, so if a message contains only inline attachments, this property is false. To verify the existence of inline attachments, parse the body property to look for a src attribute, such as <IMG src='cid:image001.jpg@01D26CD8.6C05F070'>."
+          ).nullish(),
+          importance: microsoft_graph_importance.optional(),
+          inferenceClassification: microsoft_graph_inferenceClassificationType.optional(),
+          internetMessageHeaders: z.array(microsoft_graph_internetMessageHeader).describe(
+            "A collection of message headers defined by RFC5322. The set includes message headers indicating the network path taken by a message from the sender to the recipient. It can also contain custom message headers that hold app data for the message.  Returned only on applying a $select query option. Read-only."
+          ).optional(),
+          internetMessageId: z.string().describe("The message ID in the format specified by RFC2822.").nullish(),
+          isDeliveryReceiptRequested: z.boolean().describe("Indicates whether a read receipt is requested for the message.").nullish(),
+          isDraft: z.boolean().describe(
+            "Indicates whether the message is a draft. A message is a draft if it hasn't been sent yet."
+          ).nullish(),
+          isRead: z.boolean().describe("Indicates whether the message has been read.").nullish(),
+          isReadReceiptRequested: z.boolean().describe("Indicates whether a read receipt is requested for the message.").nullish(),
+          parentFolderId: z.string().describe("The unique identifier for the message's parent mailFolder.").nullish()
+        }).strict().passthrough()
+      }
+    ],
+    response: z.void()
+  },
   {
     method: "delete",
     path: "/me/messages/:messageId",

package/logs/mcp-server.log

@@ -1,5 +1,5 @@
-2026-01-27 20:03:08 INFO: Using environment variables for secrets
-2026-01-27 20:03:08 INFO: Using environment variables for secrets
-2026-01-27 20:03:08 INFO: Using environment variables for secrets
-2026-01-27 20:03:08 INFO: Using environment variables for secrets
-2026-01-27 20:03:08 INFO: Using environment variables for secrets
+2026-01-30 18:09:24 INFO: Using environment variables for secrets
+2026-01-30 18:09:24 INFO: Using environment variables for secrets
+2026-01-30 18:09:24 INFO: Using environment variables for secrets
+2026-01-30 18:09:24 INFO: Using environment variables for secrets
+2026-01-30 18:09:24 INFO: Using environment variables for secrets

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@softeria/ms-365-mcp-server",
-  "version": "0.31.1",
+  "version": "0.32.0",
   "description": " A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API",
   "type": "module",
   "main": "dist/index.js",

package/src/endpoints.json

@@ -84,6 +84,12 @@
     "toolName": "move-mail-message",
     "scopes": ["Mail.ReadWrite"]
   },
+  {
+    "pathPattern": "/me/messages/{message-id}",
+    "method": "patch",
+    "toolName": "update-mail-message",
+    "scopes": ["Mail.ReadWrite"]
+  },
   {
     "pathPattern": "/me/messages/{message-id}/attachments",
     "method": "post",
@@ -295,8 +301,7 @@
     "pathPattern": "/me/onenote/pages/{onenotePage-id}/content",
     "method": "get",
     "toolName": "get-onenote-page-content",
-    "scopes": ["Notes.Read"],
-    "returnDownloadUrl": true
+    "scopes": ["Notes.Read"]
   },
   {
     "pathPattern": "/me/onenote/pages",