@softeria/ms-365-mcp-server 0.4.8 → 0.4.9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -26,11 +26,11 @@ A Model Context Protocol (MCP) server for interacting with Microsoft 365 service
26
26
 
27
27
  Test login in Claude Desktop:
28
28
 
29
- ![Login example](https://github.com/user-attachments/assets/e457884f-c98a-4186-9e6f-eb323ec24e0a)
29
+ ![Login example](https://github.com/user-attachments/assets/27f57f0e-57b8-4366-a8d1-c0bdab79900c)
30
30
 
31
31
  ## Examples
32
32
 
33
- ![Image](https://github.com/user-attachments/assets/1a296afb-48ed-42b0-9e7c-e685d5d1784c)
33
+ ![Image](https://github.com/user-attachments/assets/ed275100-72e8-4924-bcf2-cd8e1b4c6f3a)
34
34
 
35
35
  ## Integration
36
36
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@softeria/ms-365-mcp-server",
3
- "version": "0.4.8",
3
+ "version": "0.4.9",
4
4
  "description": "Microsoft 365 MCP Server",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -12,7 +12,7 @@ This directory contains the generated TypeScript client for the Microsoft 365 AP
12
12
  ### Version 1: AI-Generated Mappings
13
13
 
14
14
  Our initial approach used AI to map Microsoft 365 documentation and OpenAPI specifications directly into MCP tools with
15
- Zod mappings. While conceptually appealing, this approach didn't work well in practice and created several problems:
15
+ Zod mappings. While conceptually appealing, this approach didn't work well in practice and created several problems.
16
16
 
17
17
  ### Version 2: Direct OpenAPI Spec Usage
18
18