MCP server for Microsoft Teams channel workflows, including reading threads, posting new threads, replying to threads, mentioning members, and listing team members.
MCP Teams Server can start new channel threads, reply to existing threads, mention members, read thread replies, list channel threads, look up members by name, and list team members., Posting or replying in Microsoft Teams can notify real teammates and create persistent workplace records., Mentioning a member can trigger direct notifications, so require human review before allowing model-generated mentions., Channel read tools can expose existing conversations, replies, message IDs, pagination cursors, and team member context to the model., The required Microsoft Graph permission includes ChannelMessage.Read.All resource-specific consent, and Teams app permissions include message send/read and member read scopes., Use a dedicated bot application, scoped Team ID, scoped Channel ID, least-privilege permissions, and explicit approval for every write operation., Launch with `uvx --from git+https://github.com/InditexTech/mcp-teams-server mcp-teams-server` or from a verified checkout; do not use plain `uv run mcp-teams-server` from untrusted workspaces because local projects, virtual environments, or PATH entries can hijack the executable while receiving Teams secrets.
Privacy notes
Teams channels can contain customer data, employee names, emails, incident details, roadmap discussions, support conversations, credentials, links, and confidential attachments or references., Tool calls and logs can expose TEAMS_APP_ID, tenant IDs, team IDs, channel IDs, thread IDs, message IDs, member names, member emails, message bodies, replies, mentions, and pagination cursors., TEAMS_APP_PASSWORD, client secrets, tenant IDs, bot configuration, and `.env` files should stay out of prompts, issues, logs, screenshots, and committed files., Claude-generated messages may become discoverable records under organization retention, compliance, and eDiscovery policies.
Author
InditexTech
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
7 safety and 4 privacy notes across 4 risk areas. Review closely: credentials & tokens, permissions & scopes.
4 areas
SafetyGeneralMCP Teams Server can start new channel threads, reply to existing threads, mention members, read thread replies, list channel threads, look up members by name, and list team members.
SafetyData retentionPosting or replying in Microsoft Teams can notify real teammates and create persistent workplace records.
SafetyGeneralMentioning a member can trigger direct notifications, so require human review before allowing model-generated mentions.
SafetyGeneralChannel read tools can expose existing conversations, replies, message IDs, pagination cursors, and team member context to the model.
SafetyPermissions & scopesThe required Microsoft Graph permission includes ChannelMessage.Read.All resource-specific consent, and Teams app permissions include message send/read and member read scopes.
SafetyPermissions & scopesUse a dedicated bot application, scoped Team ID, scoped Channel ID, least-privilege permissions, and explicit approval for every write operation.
SafetyCredentials & tokensLaunch with `uvx --from git+https://github.com/InditexTech/mcp-teams-server mcp-teams-server` or from a verified checkout; do not use plain `uv run mcp-teams-server` from untrusted workspaces because local projects, virtual environments, or PATH entries can hijack the executable while receiving Teams secrets.
PrivacyCredentials & tokensTeams channels can contain customer data, employee names, emails, incident details, roadmap discussions, support conversations, credentials, links, and confidential attachments or references.
PrivacyData retentionTool calls and logs can expose TEAMS_APP_ID, tenant IDs, team IDs, channel IDs, thread IDs, message IDs, member names, member emails, message bodies, replies, mentions, and pagination cursors.
PrivacyCredentials & tokensTEAMS_APP_PASSWORD, client secrets, tenant IDs, bot configuration, and `.env` files should stay out of prompts, issues, logs, screenshots, and committed files.
PrivacyData retentionClaude-generated messages may become discoverable records under organization retention, compliance, and eDiscovery policies.
Safety notes
MCP Teams Server can start new channel threads, reply to existing threads, mention members, read thread replies, list channel threads, look up members by name, and list team members.
Posting or replying in Microsoft Teams can notify real teammates and create persistent workplace records.
Mentioning a member can trigger direct notifications, so require human review before allowing model-generated mentions.
Channel read tools can expose existing conversations, replies, message IDs, pagination cursors, and team member context to the model.
The required Microsoft Graph permission includes ChannelMessage.Read.All resource-specific consent, and Teams app permissions include message send/read and member read scopes.
Use a dedicated bot application, scoped Team ID, scoped Channel ID, least-privilege permissions, and explicit approval for every write operation.
Launch with `uvx --from git+https://github.com/InditexTech/mcp-teams-server mcp-teams-server` or from a verified checkout; do not use plain `uv run mcp-teams-server` from untrusted workspaces because local projects, virtual environments, or PATH entries can hijack the executable while receiving Teams secrets.
Privacy notes
Teams channels can contain customer data, employee names, emails, incident details, roadmap discussions, support conversations, credentials, links, and confidential attachments or references.
Tool calls and logs can expose TEAMS_APP_ID, tenant IDs, team IDs, channel IDs, thread IDs, message IDs, member names, member emails, message bodies, replies, mentions, and pagination cursors.
TEAMS_APP_PASSWORD, client secrets, tenant IDs, bot configuration, and `.env` files should stay out of prompts, issues, logs, screenshots, and committed files.
Claude-generated messages may become discoverable records under organization retention, compliance, and eDiscovery policies.
Prerequisites
Python 3.10 and uv/uvx available to the MCP client runtime.
Microsoft Teams account and a Team/Channel where the bot app is installed.
Microsoft Entra ID application registration with client secret credentials.
Azure Bot registration connected to the Microsoft Teams channel.
Microsoft Graph and Teams application permissions scoped to the intended team or group.
TEAMS_APP_ID, TEAMS_APP_PASSWORD, TEAMS_APP_TYPE, TEAMS_APP_TENANT_ID, TEAM_ID, and TEAMS_CHANNEL_ID configured securely.
MCP Teams Server is an MCP server implementation for Microsoft Teams channel
workflows. It lets Claude and other MCP clients read channel threads and
replies, start new channel threads, reply to existing threads, mention members,
look up members by name, and list team members.
The server is maintained by InditexTech and uses Microsoft Entra ID, Azure Bot,
Microsoft Teams app setup, Bot Framework, and Microsoft Graph configuration. It
is scoped by TEAM_ID and TEAMS_CHANNEL_ID, so teams should configure a
dedicated bot app for the exact channel Claude may access.
These sources were reviewed on 2026-06-06. Prefer the live repository,
README, Teams setup guide, LLM installation guide, package metadata, source
implementation, sample environment file, and license for current setup steps,
required permissions, environment variables, tool behavior, and licensing.
Features
Microsoft Teams channel integration through Bot Framework and Microsoft Graph.
start_thread tool for creating a new channel thread with title and content.
update_thread tool for replying to an existing thread.
read_thread tool for reading replies in a thread.
list_threads tool for paginated channel thread listing.
get_member_by_name tool for finding a member by display name.
list_members tool for listing team members.
Optional member mentions when starting or updating a thread.
Environment configuration for Entra app ID, client secret, tenant, team, and channel.
Local uv execution and pre-built GHCR container image documented upstream.
Apache-2.0 license.
Installation
After registering the Entra application, Azure Bot, Teams application, and
required permissions from the upstream setup guide, configure an MCP client with
the dedicated bot credentials:
Use a channel created for model-assisted workflows first, and test reads before
allowing the model to post or mention teammates.
Use Cases
Ask Claude to list recent threads in an approved Teams channel.
Read a specific thread before drafting a response.
Post a reviewed incident summary or deployment note to a team channel.
Reply to a thread with a human-approved update.
Mention a named teammate only after confirming the target person.
List members to validate a mention target before posting.
Route model-generated summaries into a dedicated operational Teams channel.
Safety and Privacy
MCP Teams Server can create visible workplace messages. Require human approval
before posting, replying, or mentioning anyone, and keep the bot scoped to a
specific team and channel. Test in a non-production channel before connecting it
to incident, customer, executive, HR, legal, or security channels.
Teams conversations often contain confidential business context and personal
data. Protect client secrets and tenant details, review organization retention
and eDiscovery policies, and avoid exposing private messages or member data to
model sessions that are not approved for that workspace.
Disclosure
This project is maintained by InditexTech and integrates with Microsoft Teams,
Microsoft Entra ID, Azure Bot, and Microsoft Graph. This listing is not
sponsored, paid, or affiliate-driven, and it is scoped to the source-backed MCP
server repository.
Duplicate Check
Existing content includes a CLI for Microsoft 365 MCP Server that can cover
broader Microsoft 365 tasks, and a meeting bot entry that mentions Microsoft
Teams. This entry is distinct because it covers InditexTech/mcp-teams-server,
an MCP server focused specifically on Microsoft Teams channel threads, replies,
mentions, and member listing. No matching source URL entry was found in
content/mcp.
Show that MCP Teams Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/mcp-teams-server)
How it compares
MCP Teams Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
MCP server for Microsoft Teams channel workflows, including reading threads, posting new threads, replying to threads, mentioning members, and listing team members.
Microsoft 365 Graph API MCP server for personal and organization accounts, with OAuth, read-only mode, scope allowlists, presets, multi-account support, and Streamable HTTP deployment.
MCP server for CLI for Microsoft 365 that lets Claude use natural language to search command docs and run Microsoft 365 management commands for Entra ID, SharePoint, Teams, Outlook, OneDrive, Planner, Power Platform, and more.
✓MCP Teams Server can start new channel threads, reply to existing threads, mention members, read thread replies, list channel threads, look up members by name, and list team members.
Posting or replying in Microsoft Teams can notify real teammates and create persistent workplace records.
Mentioning a member can trigger direct notifications, so require human review before allowing model-generated mentions.
Channel read tools can expose existing conversations, replies, message IDs, pagination cursors, and team member context to the model.
The required Microsoft Graph permission includes ChannelMessage.Read.All resource-specific consent, and Teams app permissions include message send/read and member read scopes.
Use a dedicated bot application, scoped Team ID, scoped Channel ID, least-privilege permissions, and explicit approval for every write operation.
Launch with `uvx --from git+https://github.com/InditexTech/mcp-teams-server mcp-teams-server` or from a verified checkout; do not use plain `uv run mcp-teams-server` from untrusted workspaces because local projects, virtual environments, or PATH entries can hijack the executable while receiving Teams secrets.
✓Without `--read-only`, enabled Microsoft Graph tools can create, update, send, delete, or otherwise change Microsoft 365 data.
Organization mode exposes broader work-account surfaces including Teams, SharePoint, shared mailboxes, online meetings, users, presence, and search.
Use `--preset`, `--enabled-tools`, `--allowed-scopes`, and `--read-only` to keep the tool surface smaller than the default.
HTTP mode requires OAuth bearer tokens for MCP requests and should be served only from trusted hosts with reviewed redirect URI allowlists.
Local stdio mode can cache Microsoft tokens in the OS credential store or fallback files; protect cache paths and account pinning settings.
Bring-your-own-token mode and Azure Key Vault integration require careful secret handling and rotation policies.
✓The MCP server does not authenticate by itself; it reuses the existing CLI for Microsoft 365 authentication context.
The m365RunCommand tool can run CLI for Microsoft 365 commands that manage Entra ID, OneDrive, OneNote, Outlook, Planner, Power Apps, Power Automate, Power Platform, SharePoint Embedded, SharePoint Online, Teams, Viva Engage, and other tenant surfaces.
Natural-language prompts may result in a chain of CLI commands, so review the resolved command docs and exact proposed operations before execution.
Commands can create teams, lists, columns, items, Planner plans, Power Platform changes, flow state changes, posts, permissions, and other tenant resources.
Prefer MFA-capable interactive or browser authentication for user sessions and certificate or secret authentication only for reviewed automation scenarios.
Avoid username and password authentication when possible because the upstream best-practices guide notes MFA limitations.
✓Vexa MCP can request bots to join meetings, stop bots, parse meeting links, read transcripts, manage recordings, create transcript share links, send and read meeting chat, make the bot speak, share screen content, update bot config, connect calendars, and configure webhooks.
Meeting URLs, IDs, passcodes, bot names, platform names, participant data, recordings, transcript share links, and API keys require careful handling.
Public transcript share links and recording download URLs should be short-lived and shared only with approved recipients.
Interactive bot tools can visibly act in live meetings; require human approval before using chat, speech, or screen-sharing tools.
The service README includes a DoD table that marks several MCP checks as untested, so validate the exact deployment path before production use.
Privacy notes
✓Teams channels can contain customer data, employee names, emails, incident details, roadmap discussions, support conversations, credentials, links, and confidential attachments or references.
Tool calls and logs can expose TEAMS_APP_ID, tenant IDs, team IDs, channel IDs, thread IDs, message IDs, member names, member emails, message bodies, replies, mentions, and pagination cursors.
TEAMS_APP_PASSWORD, client secrets, tenant IDs, bot configuration, and `.env` files should stay out of prompts, issues, logs, screenshots, and committed files.
Claude-generated messages may become discoverable records under organization retention, compliance, and eDiscovery policies.
✓Tool calls can expose email, calendar events, contacts, OneDrive files, Excel workbook data, OneNote pages, tasks, Planner data, Teams chats, SharePoint lists, user directory data, meeting details, and search results.
OAuth tokens, client IDs, tenant IDs, client secrets, selected account metadata, token cache paths, and Key Vault URLs are sensitive configuration.
Multi-account mode can reveal account usernames, account selection state, and which account handled a request.
Audit logs intentionally avoid tool parameters and Graph response bodies, but still record request IDs, user principal names, tool names, HTTP method, status, duration, and error classifications.
Microsoft Graph data may be governed by tenant retention, legal hold, compliance, GDPR, HIPAA, PIPEDA, SOC 2, or customer confidentiality rules.
✓CLI output can expose tenant IDs, user profiles, group membership, emails, calendar or Outlook data, Teams messages, SharePoint URLs, list contents, Planner tasks, flow names, app metadata, and Power Platform environment details.
Microsoft 365 tokens, certificates, client secrets, tenant IDs, site URLs, user IDs, and generated command output should stay out of prompts, issues, logs, screenshots, and committed files.
Tenant-management transcripts may contain regulated business data, employee data, customer data, or internal collaboration records.
Configure output and error handling carefully so sensitive command output is not written into persistent chat logs or debug logs unnecessarily.
✓Audio, transcripts, speaker labels, meeting metadata, chat messages, recordings, screenshots, participant names, calendar events, webhook payloads, meeting notes, API keys, and tool results may be visible to the MCP client and model provider.
Hosted Vexa sends meeting data to Vexa-operated infrastructure; self-hosted deployments still may use hosted transcription tokens unless fully self-hosting transcription.
Browser bot sessions can persist authenticated browser state through storage such as S3-compatible backends.
Logs, databases, object storage, share links, webhook receivers, and AI prompts can retain sensitive meeting content after a call ends.
Prerequisites
Python 3.10 and uv/uvx available to the MCP client runtime.
Microsoft Teams account and a Team/Channel where the bot app is installed.
Microsoft Entra ID application registration with client secret credentials.
Azure Bot registration connected to the Microsoft Teams channel.
Node.js 20 or newer recommended for the current package.
Personal Microsoft account or Microsoft Entra work/school account with approved Graph access.
Microsoft Graph permissions reviewed with `--list-permissions` for the selected preset, tools, org mode, and allowed scopes.
Admin consent or tenant approval for organization tools such as Teams, SharePoint, shared mailboxes, users, presence, and meetings.
Node.js 20 or newer.
CLI for Microsoft 365 installed globally.
Authenticated CLI for Microsoft 365 session created with an approved m365 login method.
CLI configuration reviewed for prompt handling, output format, and detailed error help.
Node.js and npx available for the `mcp-remote` client bridge.
Vexa API key for hosted Vexa or an approved self-hosted Vexa deployment.
Meeting organizer permission and participant consent before joining, recording, transcribing, chatting, speaking, or screen-sharing through a bot.
Platform policy review for Google Meet, Microsoft Teams, and Zoom bot participation.