# InditexTech/mcp-teams-server [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://github.com/InditexTech/mcp-teams-server  
**GitHub Stars:** 397  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/inditextech-mcp-teams-server

## Description
MCP server that integrates Microsoft Teams messaging (read, post, mention, list members and threads)

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "mcp-teams-server": {
    "command": "npx",
    "args": ["-y","inditextech-mcp-teams-server"],
    "env": {
      "TEAMS_APP_ID": "",
      "TEAMS_APP_PASSWORD": "",
      "TEAMS_APP_TENANT_ID": "",
      "TEAM_ID": "",
      "TEAMS_CHANNEL_ID": ""
    }
  }
}
```

**Requires environment variables:** `TEAMS_APP_ID`, `TEAMS_APP_PASSWORD`, `TEAMS_APP_TENANT_ID`, `TEAM_ID`, `TEAMS_CHANNEL_ID` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What InditexTech/mcp-teams-server MCP server does

InditexTech/mcp-teams-server MCP server connects an MCP-compatible client with Microsoft Teams. It focuses on channel conversations and team membership rather than providing a general Microsoft Graph interface.

The available operations cover common thread workflows:

- Start a channel thread with a title and message content.
- Add replies to an existing thread.
- Mention users when creating or updating messages.
- Read replies belonging to a thread.
- Read messages in a channel.
- List members of the team associated with a channel.

This makes the project suitable for agents that need to inspect team discussions, publish updates, or address specific members in Teams conversations.

## How it works

The InditexTech/mcp-teams-server MCP server is a Python application launched with the `mcp-teams-server` command. Its default transport is MCP stdio, which is appropriate for local desktop clients that start the process themselves. It also supports Streamable HTTP for an HTTP deployment and retains an SSE transport for older clients.

Microsoft Teams and Azure configuration must be completed before the server can access conversations. The application uses an MS Entra application ID, client secret, and tenant information, along with identifiers for the target team and channel. The channel identifier must use URL-escaped characters as required by the configuration.

## Setup and configuration

The documented local setup requires Python 3.12 and the uv package manager. After cloning the repository, create the environment and install its dependencies with:

```bash
uv venv
uv sync --frozen --all-extras --dev
```

Configure these variables in the shell or an `.env` file:

- `TEAMS_APP_ID`: MS Entra application UUID.
- `TEAMS_APP_PASSWORD`: client secret.
- `TEAMS_APP_TENANT_ID`: tenant UUID for a single-tenant setup.
- `TEAM_ID`: Microsoft Teams group or team ID.
- `TEAMS_CHANNEL_ID`: target channel ID with escaped URL characters.

The project also provides a container image through GitHub Container Registry and documents Docker execution with an environment file. Streamable HTTP can be exposed from the container on port 8000.

## Tools and capabilities

The InditexTech/mcp-teams-server MCP server supports message creation and reading at both channel and thread levels. Agents can begin a titled thread, append replies, retrieve thread replies, and read channel messages. Mentions are supported when starting threads or posting replies, allowing an agent to direct a message to selected team members. A member-listing capability can provide the users associated with the channel’s team.

## Limitations and notes

The README requires a Microsoft Teams account with the necessary setup and points to a separate document for Azure and Teams configuration. That document is described as guidance rather than a complete step-by-step procedure.

The supplied material does not identify specific MCP client products as supported clients. It documents stdio, Streamable HTTP, and legacy SSE transports instead. Integration tests require additional test-only variables, including thread, message, and user values; these are not part of the normal runtime configuration.

_Full upstream README: https://allmcps.com/mcp/inditextech-mcp-teams-server/readme_