MCP Microsoft Teams Server
The MCP Microsoft Teams Server enables integration with Microsoft Teams channels and threads to manage messages and members.
Capabilities include:
Start new threads with title, content, and optional member mentions
Update existing threads with new content and mentions
Read replies in specific threads
List threads in a channel with pagination support
Get member details by name
List all team members
Facilitates GitHub repository interaction and access, as seen in the repository badges and references.
Displays dynamic badges for license and release information in the repository documentation.
Provides code quality metrics integration as shown in the badges for bugs, maintainability, and reliability ratings.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Microsoft Teams Server post a message to the engineering channel about the deployment status"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Teams Server
An MCP (Model Context Protocol) server implementation for Microsoft Teams integration, providing capabilities to read messages, create messages, reply to messages, mention members.
Features
https://github.com/user-attachments/assets/548a9768-1119-4a2d-bd5c-6b41069fc522
Start thread in channel with title and contents, mentioning users
Update existing threads with message replies, mentioning users
Read thread replies
List channel team members
Read channel messages
Related MCP server: Teams Messenger MCP App
Prerequisites
uv package manager
Microsoft Teams account with proper set-up
Installation
Clone the repository:
git clone https://github.com/InditexTech/mcp-teams-server
cd mcp-teams-serverCreate a virtual environment and install dependencies:
uv venv
uv sync --frozen --all-extras --devTeams configuration
Please read this document to help you to configure Microsoft Teams and required Azure resources. It is not a step-by-step guide but can help you figure out what you will need.
Usage
Set up the following environment variables in your shell or in an .env file. You can use sample file as a template:
Key | Description |
TEAMS_APP_ID | UUID for your MS Entra ID application ID |
TEAMS_APP_PASSWORD | Client secret |
TEAMS_APP_TENANT_ID | Tenant uuid in case of SingleTenant |
TEAM_ID | MS Teams Group Id or Team Id |
TEAMS_CHANNEL_ID | MS Teams Channel ID with url escaped chars |
Start the server:
uv run mcp-teams-serverThe default MCP transport is stdio. You can also use streamable-http for HTTP deployments:
uv run mcp-teams-server --transport streamable-httpThe legacy sse transport is still available for older clients.
Development
Integration tests require the set-up the following environment variables:
Key | Description |
TEST_THREAD_ID | timestamp of the thread id |
TEST_MESSAGE_ID | timestamp of the message id |
TEST_USER_NAME | test user name |
uv run pytest -m integrationPre-built docker image
There is a pre-built image hosted in ghcr.io. You can install this image by running the following command
docker pull ghcr.io/inditextech/mcp-teams-server:latestBuild docker image
A docker image is available to run MCP server. You can build it with the following command:
docker build . -t inditextech/mcp-teams-serverRun docker image
Basic run configuration:
docker run -it inditextech/mcp-teams-serverRun with environment variables from .env file:
docker run --env-file .env -it inditextech/mcp-teams-serverRun with Streamable HTTP transport:
docker run --env-file .env -p 8000:8000 -it inditextech/mcp-teams-server --transport streamable-httpSetup LLM to use MCP Teams Server
Please follow instructions on the following document
Changelog
See CHANGELOG.md for a list of changes and version history.
Contributing
Please read CONTRIBUTING.md for details on our code of conduct and the process for submitting pull requests.
Security
For security concerns, please see our Security Policy.
License
This project is licensed under the Apache-2.0 file for details.
© 2025 INDUSTRIA DE DISEÑO TEXTIL S.A. (INDITEX S.A.)
Available Tools
6 toolsget_member_by_nameB
Get a member by its name
Inputs: name (required).
list_membersA
List all members in the team
Inputs: page_size. Returns: result
list_threadsA
List threads in channel with pagination
Inputs: limit, cursor. Returns: items, limit, total, cursor
read_threadA
Read replies in a thread
Inputs: thread_id (required), limit, cursor. Returns: items, limit, total, cursor
start_threadA
Start a new thread with a given title and content
Inputs: title (required), content (required), member_name. Returns: title, content, thread_id
update_threadB
Update an existing thread with new content
Inputs: content (required), thread_id (required), member_name. Returns: content, thread_id, message_id
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool targets a distinct resource-action pair: thread lifecycle (start/update/read/list) and member lookup (get by name/list). There is no meaningful overlap, and the descriptions make the boundary between read_thread and list_threads clear.
All tools follow a consistent snake_case verb_noun pattern such as start_, update_, read_, list_, and get_. The verb choices are predictable and match the operation being performed.
Six tools is well-scoped for a Teams server covering thread management and member lookup. There are no redundant tools, and the set feels appropriately sized for its stated domain.
Threads have start, read, update, and list coverage, while members have get and list coverage. Missing thread deletion and explicit reply/send-message operations are minor gaps, but the core workflows agents would likely need are covered.
Maintenance
Related MCP Connectors
An MCP server that let you interact with Cycloid.io Internal Development Portal and Platform
One OAuth connector for your team's remote MCP servers, with Tool Packs, guardrails and logs.
One MCP server for all your work accounts: Slack, Teams, Google Chat, Jira, ClickUp, digest, tasks.
Discover MCP servers and A2A agents; verify, message, post, follow, react, and receive webhooks.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that bridges Microsoft Teams and MCP-compatible clients, enabling chat integration, message handling, and advanced search capabilities without REST API endpoints.1-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that bridges Microsoft Teams with MCP-compatible clients (LLMs, agentic frameworks, CLI), enabling chat integration, message search, and event streaming without traditional REST API endpoints.-
- FlicenseNot gradedqualityBmaintenanceMCP server providing access to Microsoft Teams chats/channels, Outlook emails, calendar events, and SharePoint files via Microsoft Graph API.-
- AlicenseBqualityDmaintenanceMCP server for Microsoft Teams that exposes 73 tools to manage teams, channels, chats, messages, meetings, planner, calendar, apps, tabs, scheduling, search, and authentication via the Graph API.737 npmMIT