# MCP Teams Server — Microsoft Teams Tools

> mcp-teams-server exposes Microsoft Teams tools via MCP; verified 373★ and ships uv-based setup plus a GHCR Docker image.

## Install

Merge the JSON below into your `.mcp.json`:

## Quick Use

```bash
git clone https://github.com/InditexTech/mcp-teams-server && cd mcp-teams-server
uv venv && uv sync --frozen --all-extras --dev
uv run mcp-teams-server
```

## Intro

mcp-teams-server exposes Microsoft Teams tools via MCP; verified 373★ and ships uv-based setup plus a GHCR Docker image.

**Best for:** Ops/support teams who want an agent to read threads, post replies, and mention members in Teams

**Works with:** Python 3.10 + uv (recommended) or Docker; requires Azure/Teams app credentials via env vars

**Setup time:** 15-30 minutes

### Key facts (verified)

- GitHub: 373 stars · 34 forks · pushed 2026-05-13.
- License: Apache-2.0 · owner avatar + repo URL verified via GitHub API.
- README-backed entrypoint: `uv run mcp-teams-server`.

## Main

- Treat credentials as production secrets: store `TEAMS_APP_PASSWORD` in a secret manager; use `.env` only for local dev.

- Start read-only: list members and read threads first; add posting/replies after you validate tenant/channel IDs.

- Use Docker for repeatability once configs are stable; keep env templates in VCS without secrets.

### Source-backed notes

- README prerequisites list Python 3.10 and uv; install uses `uv venv` + `uv sync` and run uses `uv run mcp-teams-server`.
- README documents required env vars like `TEAMS_APP_ID`, `TEAMS_APP_PASSWORD`, and `TEAM_ID` / `TEAMS_CHANNEL_ID`.
- README includes a prebuilt GHCR image (`docker pull ghcr.io/inditextech/mcp-teams-server:latest`).

### FAQ

- **Do I need Azure setup?**: Yes — README points to a Teams/Azure setup doc for app registration and permissions.
- **Can I run it in Docker?**: Yes — README provides build and run commands and supports `--env-file .env`.
- **What’s the safest first test?**: Read a thread and list members in a non-production channel before enabling posting.

## Source & Thanks

> Source: https://github.com/InditexTech/mcp-teams-server
> License: Apache-2.0
> GitHub stars: 373 · forks: 34

---

<!-- ZH -->

## Quick Use

```bash
git clone https://github.com/InditexTech/mcp-teams-server && cd mcp-teams-server
uv venv && uv sync --frozen --all-extras --dev
uv run mcp-teams-server
```

## Intro

mcp-teams-server 通过 MCP 暴露 Microsoft Teams 的读写工具（读线程/发帖/回复/@成员）；已验证 373★，支持 uv 安装与 GHCR 镜像，并通过 `.env` 配置 Azure/Teams 凭证。

**Best for:** 运维/支持团队：希望 agent 能读线程、回复消息并在 Teams 中 @ 成员

**Works with:** Python 3.10 + uv（推荐）或 Docker；通过环境变量配置 Azure/Teams 应用凭证

**Setup time:** 15-30 minutes

### Key facts (verified)

- GitHub：373 stars · 34 forks；最近更新 2026-05-13。
- 许可证：Apache-2.0；作者头像与仓库链接均已通过 GitHub API 复核。
- README 中可对照的入口命令：`uv run mcp-teams-server`。

## Main

- 把凭证当生产级 secrets：`TEAMS_APP_PASSWORD` 放进密钥管理；`.env` 只用于本地开发。

- 先跑读操作：先列成员、读线程；确认 tenant/channel ID 无误后再开放发帖/回复。

- 配置稳定后用 Docker 提升可复现性；把 env 模板放进仓库但不要包含 secrets。

### Source-backed notes

- README 的 prerequisites 包含 Python 3.10 与 uv；安装用 `uv venv` + `uv sync`，启动用 `uv run mcp-teams-server`。
- README 列出必需环境变量：`TEAMS_APP_ID`、`TEAMS_APP_PASSWORD`、`TEAM_ID` 与 `TEAMS_CHANNEL_ID` 等。
- README 提供 GHCR 预构建镜像（`docker pull ghcr.io/inditextech/mcp-teams-server:latest`）。

### FAQ

- **需要做 Azure 配置吗？**：需要。README 指向 Teams/Azure 的配置文档用于注册应用与授权。
- **能用 Docker 跑吗？**：可以。README 给出 build/run，并支持 `--env-file .env`。
- **最安全的首测方式？**：先在非生产频道读线程与列成员，确认无误后再开放发帖能力。

## Source & Thanks

> Source: https://github.com/InditexTech/mcp-teams-server
> License: Apache-2.0
> GitHub stars: 373 · forks: 34


---
Source: https://tokrepo.com/en/workflows/mcp-teams-server-microsoft-teams-tools
Author: MCP Hub