Teams MCP

A Model Context Protocol (MCP) server that provides seamless integration with Microsoft Graph APIs, enabling AI assistants to interact with Microsoft Teams, users, chats, files, and organizational data.

<a href="https://glama.ai/mcp/servers/@floriscornel/teams-mcp">

</a>

📦 Installation

To use this MCP server in Cursor/Claude/VS Code, add the following configuration:

{
  "mcpServers": {
    "teams-mcp": {
      "command": "npx",
      "args": ["-y", "@floriscornel/teams-mcp@latest"]
    }
  }
}

🚀 Features

🔐 Authentication

👥 User Management

🏢 Microsoft Teams Integration

- Channel Operations
- List channels within teams
- Retrieve channel messages and replies
- Send messages to team channels
- Reply to existing channel threads
- Edit and soft delete channel messages and replies
- Support for message importance levels (normal, high, urgent)
- Support for inline image attachments via URL or base64 data

- Team Members
- List team members and their roles
- Access member information
- Search users for @mentions

💬 Chat & Messaging

✏️ Message Management

📎 Media & Attachments

- File Upload
- Upload and send any file type (PDF, DOCX, XLSX, ZIP, images, etc.) to channels and chats
- Large file support (>4 MB) via resumable upload sessions
- Channel uploads go to SharePoint and chat uploads go to OneDrive
- Optional message text, custom filename, formatting, and importance levels

🔍 Advanced Search & Discovery

Rich Message Formatting Support

The following tools support rich message formatting in Teams channels and chats:
- send_channel_message
- send_chat_message
- reply_to_channel_message
- update_channel_message
- update_chat_message
- send_file_to_channel
- send_file_to_chat

Format Options

You can specify the format parameter to control the message formatting:
- text (default): Plain text
- markdown: Markdown formatting (bold, italic, lists, links, code, etc.) converted to sanitized HTML

When format is set to markdown, the message content is converted to HTML using a secure markdown parser and sanitized to remove potentially dangerous content before being sent to Teams.

If format is not specified, the message will be sent as plain text.

Example Usage

{
  "teamId": "...",
  "channelId": "...",
  "message": "Bold text and _italic text_\n\n- List item 1\n- List item 2\n\nLink",
  "format": "markdown",
  "importance": "high"
}

{
  "chatId": "...",
  "message": "Simple plain text message",
  "format": "text"
}

Security Features

- HTML Sanitization: All markdown content is converted to HTML and sanitized to remove potentially dangerous elements (scripts, event handlers, etc.)
- Allowed Tags: Only safe HTML tags are permitted (p, strong, em, a, ul, ol, li, h1-h6, code, pre, etc.)
- Safe Attributes: Only safe attributes are allowed
- XSS Prevention: Content is automatically sanitized to prevent cross-site scripting attacks

Supported Markdown Features

- Text formatting: Bold (text), italic (_text_), strikethrough (~~text~~)
- Links: text
- Lists: Bulleted (- item) and numbered (1. item)
- Code: Inline ` code and fenced code blocks
- Headings: # H1 through ###### H6
- Blockquotes: > quoted text
- Tables: GitHub-flavored markdown tables

- get_chat_messages
- get_channel_messages
- get_channel_message_replies
- search_messages
- get_my_mentions

Use the contentFormat parameter to control how message content is returned:
- markdown (default): Converts Teams HTML to clean Markdown, optimized for LLM consumption
- raw: Returns the original HTML from the Microsoft Graph API

| HTML Element | Markdown Output |
| -------------------------------------- | --------------------------------------------------------- |
| <at id="0">Name</at> (Teams mention) | @Name (multi-word names merged using mentions metadata) |
| <strong>text</strong> | text |
| <em>text</em> | text |
| <code>text</code> | text |
| <a href="url">text</a> | text |
| <ul><li>item</li></ul> | - item |
| <table>...</table> | GFM Markdown table |
| <attachment id="..."> | {attachment:id} |
| <systemEventMessage/> | (removed) |
| <hr> | --- |
| &nbsp;, &amp;, etc. | Decoded to plain characters |

Messages that contain file attachments or inline images include an attachments array in the response with metadata for each attachment (id, name, contentType, contentUrl, thumbnailUrl). The inline {attachment:id} markers in the markdown content correlate with entries in this array, allowing consumers to identify and download attachments via download_message_hosted_content or download_chat_hosted_content.

{
  "chatId": "19:meeting_...",
  "limit": 10,
  "contentFormat": "markdown"
}

{
  "chatId": "19:meeting_...",
  "limit": 10,
  "contentFormat": "raw"
}

``bash