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

package/README.md

@@ -26,11 +26,11 @@ A Model Context Protocol (MCP) server for interacting with Microsoft 365 service
 
 Test login in Claude Desktop:
 
-![Login example](https://github.com/user-attachments/assets/e457884f-c98a-4186-9e6f-eb323ec24e0a)
+![Login example](https://github.com/user-attachments/assets/27f57f0e-57b8-4366-a8d1-c0bdab79900c)
 
 ## Examples
 
-![Image](https://github.com/user-attachments/assets/1a296afb-48ed-42b0-9e7c-e685d5d1784c)
+![Image](https://github.com/user-attachments/assets/ed275100-72e8-4924-bcf2-cd8e1b4c6f3a)
 
 ## Integration
 
@@ -103,6 +103,8 @@ Environment variables:
 - `READ_ONLY=true|1`: Alternative to --read-only flag
 - `LOG_LEVEL`: Set logging level (default: 'info')
 - `SILENT=true`: Disable console output
+- `MS365_MCP_CLIENT_ID`: Custom Azure app client ID (defaults to built-in app)
+- `MS365_MCP_TENANT_ID`: Custom tenant ID (defaults to 'common' for multi-tenant)
 
 ## Support
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@softeria/ms-365-mcp-server",
-  "version": "0.4.7",
+  "version": "0.4.9",
   "description": "Microsoft 365 MCP Server",
   "type": "module",
   "main": "dist/index.js",

package/src/generated/README.md

@@ -2,30 +2,28 @@
 
 This directory contains the generated TypeScript client for the Microsoft 365 API based on the OpenAPI specification.
 
-> **Important Note for NPM Package Users**: 
-> The source file `client.ts` (approximately 1MB) is excluded from the npm package to reduce package size, 
+> **Important Note for NPM Package Users**:
+> The source file `client.ts` (approximately 1MB) is excluded from the npm package to reduce package size,
 > but the compiled JavaScript file `client.js` is included. This means the package is fully functional,
 > but you won't see the TypeScript source in the node_modules directory.
 
 ## The Evolution
 
-### Initial Challenge
+### Version 1: AI-Generated Mappings
 
-Our initial approach used the full MS 365 OpenAPI specification file directly. This created several significant problems:
+Our initial approach used AI to map Microsoft 365 documentation and OpenAPI specifications directly into MCP tools with
+Zod mappings. While conceptually appealing, this approach didn't work well in practice and created several problems.
+
+### Version 2: Direct OpenAPI Spec Usage
+
+We then moved to using the full MS 365 OpenAPI specification file directly. This improved reliability but created new
+significant problems:
 
 - The spec file was a whopping 45MB in size
 - It had to be included in the npm package
 - Startup time was painfully slow due to parsing the large spec file
 
-### Exploration Phase
-
-We explored several alternatives:
-
-1. Live-parsing a trimmed version of the spec file
-2. Creating a static trimmed version
-3. Pre-generating client code
-
-### Current Solution
+### Version 3: Current Solution (Trimmed Spec + Generated Client)
 
 We eventually settled on a combined approach:
 
@@ -39,6 +37,13 @@ We eventually settled on a combined approach:
 - **Type safety** - Full TypeScript types generated from the OpenAPI spec
 - **Validation** - Zod schemas for request/response validation
 
+### Current Limitations & Future Improvements
+
+While this approach is a significant improvement, it's not perfect. The MCP server might still struggle to understand
+the MS 365 endpoints correctly, and there's room for improvements in how the API is exposed and documented for AI
+assistants. However, with the current foundation of generated TypeScript clients and proper type safety, these
+improvements should now be much easier to implement and maintain.
+
 ## Regenerating the Client
 
 To regenerate the client code (e.g., after API changes or to update the supported endpoints):