What can @softeria/ms-365-mcp-server do?

microsoft graph api resource access via mcp protocol, email reading and composition with mailbox context, calendar event querying and meeting management, onedrive and sharepoint file access with path-based navigation, user and group directory querying with azure ad integration, teams and channel message access with conversation threading, mcp server lifecycle management and tool registration

@softeria/ms-365-mcp-server

MCP ServerFree

A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API

Open Source

/ 100

7 capabilities

Capabilities7 decomposed

microsoft graph api resource access via mcp protocol

Medium confidence

Exposes Microsoft 365 resources (users, groups, mail, calendar, files, teams) through the Model Context Protocol by implementing MCP server endpoints that translate client requests into authenticated Graph API calls. Uses OAuth 2.0 client credentials or delegated auth flows to obtain tokens, then marshals HTTP requests to Microsoft's REST endpoints and transforms JSON responses back through MCP's tool/resource interface.

Solves for

I want my AI agent to read and write emails from an Office 365 mailboxI need to query user directory and group membership data from Azure ADI want to access files and folders stored in OneDrive or SharePointI need to retrieve calendar events and meeting details from Outlook

Best for

Enterprise teams building AI agents that need M365 integration

Developers automating Office 365 workflows through LLM-powered interfaces

Organizations standardizing on MCP for multi-service AI orchestration

Requires

Node.js 16+

Microsoft 365 tenant with admin access to register application

Azure AD application with Graph API permissions (Mail.Read, Calendar.Read, Files.Read, etc.)

Limitations

Requires valid Microsoft 365 tenant and application registration in Azure AD

Rate limiting applies per Graph API quotas (typically 2000 requests per 20 seconds per app)

Token refresh logic must handle expiry; no built-in token caching strategy documented

What makes it unique

Implements MCP server pattern specifically for Graph API, translating MCP's tool/resource abstraction directly to Graph's OData query model and batch operations, enabling LLMs to compose complex M365 workflows without direct API knowledge

vs alternatives

Provides native MCP integration for M365 (vs. generic REST API wrappers), allowing Claude and other MCP clients to access Office 365 with standardized tool calling rather than custom API client libraries

email reading and composition with mailbox context

Medium confidence

Implements MCP tools to list, read, and compose emails by wrapping Graph API's /me/messages, /me/mailFolders, and /me/sendMail endpoints. Supports filtering by folder, sender, date range, and subject via OData query parameters; retrieves message bodies in both plain text and HTML; handles attachments as metadata references. Composition creates draft messages with recipients, subject, body, and attachment references before sending.

Solves for

I want to check my inbox and read recent emails from specific sendersI need to search emails by date range or keywordsI want to compose and send an email on behalf of the authenticated userI need to retrieve email attachments or check for unread message counts

Best for

AI agents handling email triage and response automation

Personal productivity assistants that need mailbox access

Workflow automation tools that compose notifications or reports via email

Requires

Mail.Read and Mail.Send Graph API permissions

User mailbox provisioned in Exchange Online

Valid OAuth token with delegated permissions (not app-only)

Limitations

Cannot access shared mailboxes without explicit delegation setup in Azure AD

Attachment handling is metadata-only; binary content not streamed through MCP

HTML email bodies may contain scripts/styles that require sanitization before display

What makes it unique

Exposes Exchange Online mailbox operations through MCP's tool interface with OData filtering support, allowing LLMs to compose natural-language email queries (e.g., 'unread emails from my manager this week') that map to efficient Graph API filters

vs alternatives

Simpler than building custom IMAP/SMTP clients; leverages Graph API's native filtering and pagination, avoiding the complexity of MIME parsing and IMAP protocol state management

calendar event querying and meeting management

Medium confidence

Provides MCP tools to list, read, and create calendar events by calling Graph API's /me/calendarview, /me/events, and /me/events POST endpoints. Supports time-range queries via startDateTime/endDateTime parameters, retrieves event details (title, time, attendees, location, body), and creates new events with attendee lists and reminders. Handles recurring events and timezone conversions via IANA timezone identifiers.

Solves for

I want to check my calendar for availability in a specific time windowI need to find meetings with specific attendees or in specific roomsI want to create a new meeting and invite attendeesI need to check if a time slot is free before scheduling

Best for

Meeting scheduling assistants and calendar automation

Availability-checking agents for resource allocation

Personal assistants that need to coordinate meetings across calendars

Requires

Calendars.Read and Calendars.ReadWrite Graph API permissions

User mailbox with Exchange Online calendar provisioned

Valid OAuth token with delegated permissions

Limitations

Recurring event expansion requires explicit date range queries; no built-in recurrence rule parsing

Attendee availability (free/busy) requires separate /me/calendar/getSchedule endpoint call

Cannot directly modify meeting organizer's calendar if user is attendee (only organizer can modify)

What makes it unique

Wraps Graph API's calendarview endpoint with timezone-aware time range queries, enabling LLMs to ask natural questions about availability ('am I free next Tuesday 2-3pm?') that translate to efficient Graph API calls with proper timezone handling

vs alternatives

More flexible than CalDAV clients for querying; Graph API's calendarview endpoint is optimized for range queries and attendee expansion, avoiding the need to parse iCalendar objects or manage subscription state

onedrive and sharepoint file access with path-based navigation

Medium confidence

Implements MCP tools to list, read metadata, and retrieve file contents from OneDrive and SharePoint via Graph API's /me/drive, /drives/{driveId}/items, and /sites/{siteId}/drive endpoints. Supports hierarchical path navigation, file search by name/type, and retrieval of file metadata (size, modified date, sharing status). File contents are returned as base64-encoded data or text previews depending on file type.

Solves for

I want to browse my OneDrive folder structure and find specific filesI need to read the contents of a document or spreadsheetI want to search for files by name or modification dateI need to check file sharing permissions and access levels

Best for

Document-aware AI agents that need to access user files

Knowledge management systems that index OneDrive/SharePoint content

Workflow automation that reads and processes Office documents

Requires

Files.Read or Files.ReadWrite Graph API permissions

OneDrive or SharePoint site provisioned for user

Valid OAuth token with delegated permissions

Limitations

Large files (>100MB) may timeout; streaming download not supported through MCP

Office document parsing (docx, xlsx, pptx) requires separate processing; Graph API returns raw binary

Shared files require explicit sharing link or delegated access; cannot access arbitrary user drives

What makes it unique

Provides path-based file navigation through Graph API's item hierarchy, allowing LLMs to traverse OneDrive/SharePoint like a filesystem while leveraging Graph's native metadata and sharing APIs

vs alternatives

Simpler than WebDAV or direct SharePoint REST calls; Graph API abstracts away site/drive ID complexity and provides unified interface for both OneDrive and SharePoint

user and group directory querying with azure ad integration

Medium confidence

Exposes MCP tools to query Azure AD users and groups via Graph API's /users, /groups, and /me/memberOf endpoints. Supports filtering by display name, email, job title, department, and group membership; retrieves user profiles (name, email, phone, office location, manager) and group details (members, owners, description). Implements pagination for large result sets using Graph API's skipToken mechanism.

Solves for

I want to find a user by email or name in the organization directoryI need to check group membership and who manages a teamI want to retrieve organizational hierarchy (manager relationships)I need to list all members of a specific group or team

Best for

Organizational lookup and people-finding agents

Team collaboration tools that need directory integration

Access control and permission management workflows

Requires

User.Read.All and Group.Read.All Graph API permissions

Azure AD tenant with users and groups provisioned

Valid OAuth token (app-only or delegated with admin consent)

Limitations

User.Read.All permission required for directory queries; may require admin consent

Manager relationships are one-level only; no built-in org chart traversal

Sensitive attributes (phone, office location) may be redacted based on privacy policies

What makes it unique

Provides OData-filtered directory queries through MCP, enabling LLMs to compose natural-language people searches ('find all engineers in the sales department') that map to efficient Graph API filter expressions

vs alternatives

More efficient than LDAP queries for cloud-native Azure AD; Graph API's OData filtering is optimized for directory searches and includes modern attributes (manager, department) without LDAP schema complexity

teams and channel message access with conversation threading

Medium confidence

Implements MCP tools to list Teams, channels, and messages via Graph API's /teams, /teams/{teamId}/channels, and /teams/{teamId}/channels/{channelId}/messages endpoints. Supports message filtering by date range and sender, retrieves message threads with replies, and accesses channel metadata (description, topic, members). Messages include sender info, timestamps, and reply counts for conversation context.

Solves for

I want to search Teams messages for specific keywords or from specific peopleI need to read recent messages in a channel to understand contextI want to retrieve conversation threads and repliesI need to list all teams and channels the user has access to

Best for

Team collaboration assistants that need message context

Knowledge extraction from Teams conversations

Notification and alert systems that monitor Teams channels

Requires

ChannelMessage.Read.All and Team.ReadBasic.All Graph API permissions

User member of Teams with channels

Valid OAuth token with delegated permissions

Limitations

Message search limited to channel messages; direct message (1:1 chat) access requires separate /chats endpoint

Full-text search across all messages requires Microsoft Search API; Graph API filtering is metadata-only

Threaded replies may require separate API calls per message to retrieve all replies

What makes it unique

Exposes Teams channel messages through MCP with conversation threading support, allowing LLMs to retrieve message context and replies without manually navigating Teams UI or managing conversation state

vs alternatives

Simpler than Teams SDK for message retrieval; Graph API abstracts away Teams client complexity and provides unified REST interface for both channel and chat access

mcp server lifecycle management and tool registration

Medium confidence

Implements the MCP server protocol by registering tools and resources with the MCP client, handling request/response serialization, and managing server initialization. Uses Node.js event emitters to handle incoming tool calls, validates request parameters against defined schemas, and returns structured responses. Manages OAuth token lifecycle (refresh, expiry handling) and connection state between MCP client and Graph API.

Solves for

I want to set up an MCP server that exposes M365 capabilities to my LLM clientI need to ensure my MCP server properly handles authentication and token refreshI want to define which M365 tools are available to my AI agentI need to debug MCP communication between my client and the server

Best for

Developers building MCP-compatible LLM agents

Teams deploying Claude Desktop with M365 integration

Organizations standardizing on MCP for multi-service orchestration

Requires

Node.js 16+

MCP client library or compatible LLM framework (Claude Desktop, custom agent)

Valid Azure AD application registration with Graph API permissions

Limitations

No built-in persistence for server state; requires external database for audit logs or request history

Token refresh logic must be implemented per OAuth flow; no automatic token caching documented

MCP protocol version compatibility depends on client implementation; version negotiation not explicitly documented

What makes it unique

Implements full MCP server lifecycle including tool registration, request routing, and OAuth token management, providing a complete bridge between MCP clients and Graph API without requiring custom protocol implementation

vs alternatives

Eliminates need to build custom MCP server from scratch; provides pre-built tool definitions and Graph API integration patterns that would otherwise require significant engineering effort

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Related Artifactssharing capabilities

Artifacts that share capabilities with @softeria/ms-365-mcp-server, ranked by overlap. Discovered automatically through the match graph.

MCP Server34

ms-365-mcp-server

A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API

calendar event management with meeting schedulingemail reading, sending, and management via graph apimcp protocol server with graph api tool registrationoutlook contacts management and directory access

4 shared capabilities

MCP Server20

MintMCP

** - MCP servers for Google Calendar, Gmail, Outlook Calendar, and Outlook.

outlook calendar event synchronization and management via mcpoutlook email message retrieval and composition via mcpgoogle calendar event synchronization and management via mcpmulti-provider calendar and email tool orchestration via mcp

4 shared capabilities

MCP Server29

@microsoft/workiq

MCP server for Microsoft 365 Copilot

microsoft 365 resource access via mcp protocolcalendar event creation and scheduling via llm instructions

2 shared capabilities

MCP Server30

agentmail-mcp

AgentMail MCP Server

mcp-protocol-compliance-and-resource-management

1 shared capability

MCP Server25

Graphlit

** - Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a searchable [Graphlit](https://www.graphlit.com) project.

mcp resource exposure and stdio-based protocol bridging

1 shared capability

MCP Server27

@cardor/email-management

A Node.js application for managing email workflows using the ModelContextProtocol (MCP).

mcp-based email server integration

1 shared capability

Best For

✓Enterprise teams building AI agents that need M365 integration
✓Developers automating Office 365 workflows through LLM-powered interfaces
✓Organizations standardizing on MCP for multi-service AI orchestration
✓AI agents handling email triage and response automation
✓Personal productivity assistants that need mailbox access
✓Workflow automation tools that compose notifications or reports via email
✓Meeting scheduling assistants and calendar automation
✓Availability-checking agents for resource allocation

Known Limitations

⚠Requires valid Microsoft 365 tenant and application registration in Azure AD
⚠Rate limiting applies per Graph API quotas (typically 2000 requests per 20 seconds per app)
⚠Token refresh logic must handle expiry; no built-in token caching strategy documented
⚠Batch operations limited to Graph API's native batch endpoint constraints (20 requests per batch)
⚠Cannot access shared mailboxes without explicit delegation setup in Azure AD
⚠Attachment handling is metadata-only; binary content not streamed through MCP

Requirements

Node.js 16+Microsoft 365 tenant with admin access to register applicationAzure AD application with Graph API permissions (Mail.Read, Calendar.Read, Files.Read, etc.)Client ID and secret or certificate for OAuth 2.0 authenticationMCP-compatible client (Claude Desktop, custom LLM agent framework)Mail.Read and Mail.Send Graph API permissionsUser mailbox provisioned in Exchange OnlineValid OAuth token with delegated permissions (not app-only)

Input / Output

Accepts: MCP tool calls with parameters (e.g., mailbox ID, filter queries, resource paths), OAuth tokens (bearer tokens from Azure AD), Graph API query parameters (OData filters, select clauses, pagination tokens), Folder ID or well-known folder names (inbox, drafts, sentItems), OData filter strings (e.g., "from eq 'user@example.com'"), Message composition parameters (recipients, subject, body, attachments), Date/time range (startDateTime, endDateTime in ISO 8601 format), OData filter parameters (e.g., attendee email, subject keywords), Event creation payload (subject, start/end times, attendees, location, body), Drive ID or 'me' for user's default drive, Item ID or path-based navigation (e.g., '/Documents/Report.docx'), Search query parameters (name, file type, modified date range), OData filter parameters (displayName, mail, jobTitle, department), User or group ID, Pagination tokens (skipToken for large result sets), Team ID and channel ID, Date range filters (from/to dates), Sender email or display name for filtering, MCP protocol messages (tool calls with parameters), OAuth tokens and refresh tokens, Server configuration (client ID, secret, tenant ID)

Produces: JSON-serialized Microsoft Graph resources (users, messages, events, files), Structured metadata (timestamps, IDs, permissions, content previews), Error responses with Graph API error codes and descriptions, Message objects with ID, sender, subject, received date, preview text, Full message bodies (plain text or HTML), Attachment metadata (filename, size, content type, attachment ID), Event objects with ID, subject, start/end times, attendees, location, organizer, Event body/description text, Attendee response status (accepted, declined, tentative, no response), File/folder metadata (ID, name, size, modified date, MIME type, webUrl), File contents as base64-encoded data or text preview, Folder listing with child items and hierarchy information, User objects with ID, displayName, mail, jobTitle, department, manager reference, Group objects with ID, displayName, description, members, owners, Membership relationships (user -> groups, group -> members), Message objects with ID, sender, timestamp, body, reply count, Channel metadata (ID, displayName, description, topic), Team metadata (ID, displayName, description, members count), MCP protocol responses (tool results, errors), Structured tool definitions and schemas, Server status and health check responses

UnfragileRank

Adoption15%(30% weight)

Quality24%(25% weight)

Ecosystem42%(25% weight)

Match Graph10%(15% weight)

Freshness75%(5% weight)

UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.

Type: MCP Server

7 capabilities

Visit @softeria/ms-365-mcp-server→

Package Details

npm

Registry

0.85.0

Version

Weekly Downloads

About

A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API

Alternatives to @softeria/ms-365-mcp-server

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

Are you the builder of @softeria/ms-365-mcp-server?

Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.

Claim this artifact →Verification via email

Get the weekly brief

New tools, rising stars, and what's actually worth your time. No spam.

Data Sources

mcp registry

Looking for something else?

Search →

Capabilities7 decomposed

microsoft graph api resource access via mcp protocol

Medium confidence

Solves for

Best for

Enterprise teams building AI agents that need M365 integration

Developers automating Office 365 workflows through LLM-powered interfaces

Organizations standardizing on MCP for multi-service AI orchestration

Requires

Node.js 16+

Microsoft 365 tenant with admin access to register application

Azure AD application with Graph API permissions (Mail.Read, Calendar.Read, Files.Read, etc.)

Limitations

Requires valid Microsoft 365 tenant and application registration in Azure AD

Rate limiting applies per Graph API quotas (typically 2000 requests per 20 seconds per app)

Token refresh logic must handle expiry; no built-in token caching strategy documented

What makes it unique

vs alternatives

email reading and composition with mailbox context

Medium confidence

Solves for

Best for

AI agents handling email triage and response automation

Personal productivity assistants that need mailbox access

Workflow automation tools that compose notifications or reports via email

Requires

Mail.Read and Mail.Send Graph API permissions

User mailbox provisioned in Exchange Online

Valid OAuth token with delegated permissions (not app-only)

Limitations

Cannot access shared mailboxes without explicit delegation setup in Azure AD

Attachment handling is metadata-only; binary content not streamed through MCP

HTML email bodies may contain scripts/styles that require sanitization before display

What makes it unique

vs alternatives

Simpler than building custom IMAP/SMTP clients; leverages Graph API's native filtering and pagination, avoiding the complexity of MIME parsing and IMAP protocol state management

calendar event querying and meeting management

Medium confidence

Solves for

Best for

Meeting scheduling assistants and calendar automation

Availability-checking agents for resource allocation

Personal assistants that need to coordinate meetings across calendars

Requires

Calendars.Read and Calendars.ReadWrite Graph API permissions

User mailbox with Exchange Online calendar provisioned

Valid OAuth token with delegated permissions

Limitations

Recurring event expansion requires explicit date range queries; no built-in recurrence rule parsing

Attendee availability (free/busy) requires separate /me/calendar/getSchedule endpoint call

Cannot directly modify meeting organizer's calendar if user is attendee (only organizer can modify)

What makes it unique

vs alternatives

onedrive and sharepoint file access with path-based navigation

Medium confidence

Solves for

Best for

Document-aware AI agents that need to access user files

Knowledge management systems that index OneDrive/SharePoint content

Workflow automation that reads and processes Office documents

Requires

Files.Read or Files.ReadWrite Graph API permissions

OneDrive or SharePoint site provisioned for user

Valid OAuth token with delegated permissions

Limitations

Large files (>100MB) may timeout; streaming download not supported through MCP

Office document parsing (docx, xlsx, pptx) requires separate processing; Graph API returns raw binary

Shared files require explicit sharing link or delegated access; cannot access arbitrary user drives

What makes it unique

Provides path-based file navigation through Graph API's item hierarchy, allowing LLMs to traverse OneDrive/SharePoint like a filesystem while leveraging Graph's native metadata and sharing APIs

vs alternatives

Simpler than WebDAV or direct SharePoint REST calls; Graph API abstracts away site/drive ID complexity and provides unified interface for both OneDrive and SharePoint

user and group directory querying with azure ad integration

Medium confidence

Solves for

Best for

Organizational lookup and people-finding agents

Team collaboration tools that need directory integration

Access control and permission management workflows

Requires

User.Read.All and Group.Read.All Graph API permissions

Azure AD tenant with users and groups provisioned

Valid OAuth token (app-only or delegated with admin consent)

Limitations

User.Read.All permission required for directory queries; may require admin consent

Manager relationships are one-level only; no built-in org chart traversal

Sensitive attributes (phone, office location) may be redacted based on privacy policies

What makes it unique

vs alternatives

teams and channel message access with conversation threading

Medium confidence

Solves for

Best for

Team collaboration assistants that need message context

Knowledge extraction from Teams conversations

Notification and alert systems that monitor Teams channels

Requires

ChannelMessage.Read.All and Team.ReadBasic.All Graph API permissions

User member of Teams with channels

Valid OAuth token with delegated permissions

Limitations

Message search limited to channel messages; direct message (1:1 chat) access requires separate /chats endpoint

Full-text search across all messages requires Microsoft Search API; Graph API filtering is metadata-only

Threaded replies may require separate API calls per message to retrieve all replies

What makes it unique

vs alternatives

Simpler than Teams SDK for message retrieval; Graph API abstracts away Teams client complexity and provides unified REST interface for both channel and chat access

mcp server lifecycle management and tool registration

Medium confidence

Solves for

Best for

Developers building MCP-compatible LLM agents

Teams deploying Claude Desktop with M365 integration

Organizations standardizing on MCP for multi-service orchestration

Requires

Node.js 16+

MCP client library or compatible LLM framework (Claude Desktop, custom agent)

Valid Azure AD application registration with Graph API permissions

Limitations

No built-in persistence for server state; requires external database for audit logs or request history

Token refresh logic must be implemented per OAuth flow; no automatic token caching documented

MCP protocol version compatibility depends on client implementation; version negotiation not explicitly documented

What makes it unique

vs alternatives

Eliminates need to build custom MCP server from scratch; provides pre-built tool definitions and Graph API integration patterns that would otherwise require significant engineering effort

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Alternatives to @softeria/ms-365-mcp-server

IntelliCode50Extension

AI-assisted development

Compare →

GitHub Copilot Chat53Extension

AI chat features powered by Copilot

Compare →

GitHub Copilot52Extension

Your AI pair programmer

Compare →

Claude Code for VS Code52Extension

Claude Code for VS Code: Harness the power of Claude Code without leaving your IDE

Compare →

@softeria/ms-365-mcp-server

Capabilities7 decomposed

microsoft graph api resource access via mcp protocol

email reading and composition with mailbox context

calendar event querying and meeting management

onedrive and sharepoint file access with path-based navigation

user and group directory querying with azure ad integration

teams and channel message access with conversation threading

mcp server lifecycle management and tool registration

Related Artifactssharing capabilities

ms-365-mcp-server

MintMCP

@microsoft/workiq

agentmail-mcp

Graphlit

@cardor/email-management

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Package Details

About

Categories

Alternatives to @softeria/ms-365-mcp-server

Are you the builder of @softeria/ms-365-mcp-server?

Get the weekly brief

Data Sources

@softeria/ms-365-mcp-server

Capabilities7 decomposed

microsoft graph api resource access via mcp protocol

email reading and composition with mailbox context

calendar event querying and meeting management

onedrive and sharepoint file access with path-based navigation

user and group directory querying with azure ad integration

teams and channel message access with conversation threading

mcp server lifecycle management and tool registration

Related Artifactssharing capabilities

ms-365-mcp-server

MintMCP

@microsoft/workiq

agentmail-mcp

Graphlit

@cardor/email-management

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

Package Details

About

Categories

Alternatives to @softeria/ms-365-mcp-server

Are you the builder of @softeria/ms-365-mcp-server?

Get the weekly brief

Data Sources