mcp-teams-server — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor this implementation for changes in adoption, MCP interface, maintenance and permission boundary.

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Read and create Microsoft Teams channel messages

What we know

An MCP (Model Context Protocol) server implementation for Microsoft Teams integration, providing capabilities to read messages, create messages, reply to messages, mention members. Read and create Microsoft Teams channel messages.

Maintenance / activity evidence

GitHub REST pushed_at 2026-10-02T07:57:39Z

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Scoped by connected account, local OS, and configuration; verify exact permissions before installation. Reported action classes: create messages; reply to messages; mention members. Complete write authority is not verified.
Microsoft Entra application credentials and tenant/team IDs
Sensitive access: Channel messages and organisation metadata

Messages may be read, created, replied to, and mention users; permissions depend on Entra app and Teams account.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

435 repository stars

Stars observed Oct 9, 2026.

Repository total for InditexTech/mcp-teams-server.

All limitations / Review context

Has mcp-teams-server changed its specific MCP integration, install method or privilege scope, and does it justify shortlist promotion?

High-impact permissions explicitly documented; no known blocker to an accurately caveated public Radar listing in limited first-party review.

Messages may be read, created, replied to, and mention users; permissions depend on Entra app and Teams account.
Scoped by connected account, local OS, and configuration; verify exact permissions before installation.
Microsoft Entra application credentials and tenant/team IDs
Channel messages and organisation metadata
Reviewed write actions: create messages; reply to messages; mention members
Sensitive access: Channel messages and organisation metadata
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
No exhaustive advisory or runtime review performed; never infer installation safety.
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation.
Repository pushed_at explicitly observed

Original activity observations

GitHub REST pushed_at 2026-10-02T07:57:39Z

Technical identity

github.com/InditexTech/mcp-teams-server

Exact implementation source: https://github.com/InditexTech/mcp-teams-server ↗
Reviewed resource type: MCP Server
Repository identity: InditexTech/mcp-teams-server

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

GitHub repository ↗
inditextech/mcp-teams-server
Recorded repository material and project history.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 12, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Use the publisher-documented command or connection method below; complete the prerequisites and client configuration before expecting a usable MCP connection.
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
Configure / authenticate
Publisher instructions
Create a registered Microsoft Entra application and provision appropriate Teams access using the publisher doc/MS-Teams-setup.md. Set TEAMS_APP_ID, TEAMS_APP_PASSWORD, TEAMS_APP_TYPE, TEAMS_APP_TENANT_ID for single tenant, TEAM_ID and TEAMS_CHANNEL_ID in the runtime environment/.env; do not commit the client secret. The official Teams guide is advisory, not a complete automatic enrollment wizard.
Check connection
Suggested check
Confirm the server launches with its Entra and Teams variables, then inspect the client tool listing. For functional authorization test use a designated sandbox Teams channel and read-only listing; do not create/reply/send production messages.
Remove / uninstall / revoke
Stop the Teams MCP host process/container, remove the client registration/config, and separately review permissions granted to the Entra app. Stopping the process does not revoke Entra consent.

Official Documentation & Sources

What it does

An MCP (Model Context Protocol) server implementation for Microsoft Teams integration, providing capabilities to read messages, create messages, reply to messages, mention members. Read and create Microsoft Teams channel messages.

Capability: Communication
Resource type: MCP Server
Best fit: Read and create Microsoft Teams channel messages

Representative uses

Read team-channel messages
Create and reply to Teams posts
Add colleague mentions to messages
Read and create Microsoft Teams channel messages

Limitations

Messages may be read, created, replied to, and mention users; permissions depend on Entra app and Teams account.
Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation.
Repository pushed_at explicitly observed

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Microsoft Entra application credentials and tenant/team IDs
Permissions: Scoped by connected account, local OS, and configuration; verify exact permissions before installation.
Data handling: Channel messages and organisation metadata
Cost: may incur external API or infrastructure charges; unverified
Risk and cautions: Messages may be read, created, replied to, and mention users; permissions depend on Entra app and Teams account.

Access scope and cautions

Write actions: Not verified create messages reply to messages mention members
Sensitive access: Channel messages and organisation metadata
Risk level: high
Security notes: Messages may be read, created, replied to, and mention users; permissions depend on Entra app and Teams account.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-09. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Read team-channel messages; Create and reply to Teams posts; Add colleague mentions to messages; Read and create Microsoft Teams channel messages.

What setup and authentication are documented?

Recorded installation/entrypoint step: uv sync --frozen --all-extras --dev && uv run mcp-teams-server. Recorded environment-variable notes: TEAMS_APP_ID; TEAMS_APP_PASSWORD; TEAMS_APP_TYPE; TEAM_ID; TEAMS_CHANNEL_ID. No configuration values are supplied here. Prerequisites: MCP-compatible client. Client notes: Command provided only where first-party command or package existence is established; verify the client configuration against upstream documentation. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Microsoft Entra application credentials and tenant/team IDs

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: create messages; reply to messages; mention members. Recorded permission context: Scoped by connected account, local OS, and configuration; verify exact permissions before installation.

What data-handling boundary should I consider?

Channel messages and organisation metadata Recorded sensitive-access context: Channel messages and organisation metadata.

What limitations and risks should I check before use?

Messages may be read, created, replied to, and mention users; permissions depend on Entra app and Teams account. Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation. Repository pushed_at explicitly observed. No exhaustive advisory or runtime review performed; never infer installation safety.