MCP Teams Server — Microsoft Teams Tools

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.