Does this need admin consent?

Yes for most Graph scopes — admins must approve the app registration in Entra. Plan for the consent dance during onboarding.

Personal Microsoft accounts?

Tenant-bound only. The MCP targets organisational Teams tenants; personal-account chats are out of scope.

Can the agent send 1:1 messages?

Yes — chats are supported alongside channels. The user must already have a chat thread for the agent to post into (Graph cannot initiate new 1:1s freely).

Meetings — full Teams meeting control?

Basic create/list/cancel via Graph. Full meeting orchestration (lobbies, breakouts) needs richer Teams APIs not in scope here.

Microsoft Teams

Name: Top MCPs — curated MCP directory
Creator: Top MCPs
License: https://creativecommons.org/licenses/by/4.0/

Official

Read channel messages, post replies, and trigger meetings from MS Teams.

Score 83(?)MicrosoftMIT 3.6kVerified Aug 24, 2026Top MCPs for Communication →

Install View on GitHub

Quick answer

What it does

Connects via Microsoft Graph to a Microsoft Teams tenant, exposes channel/chat enumeration, message posting and reading, and basic meeting/calendar interactions.

Best for

Posting agent status to channels
Summarising channel activity
Meeting prep from calendar context
Cross-tool notifications inside Teams

Not for

Tenants without admin consent for Graph scopes
Heavy media (video, large file) workflows

Source: top-mcps.com/mcp/microsoft-teams — verified Aug 2026

Setup recipe

Pick your client, then follow the three steps.

Install

claude_desktop_config.jsonjson

{
  "mcpServers": {
    "microsoft-teams": {
      "command": "Remote",
      "args": [
        "MCP",
        "—",
        "add",
        "https://agent365.svc.cloud.microsoft/agents/tenants/YOUR_TENANT_ID/servers/mcp_TeamsServer",
        "as",
        "a",
        "connector",
        "and",
        "sign",
        "in",
        "with",
        "Entra"
      ],
      "env": {
        "AZURE_TENANT_ID": "${AZURE_TENANT_ID}"
      }
    }
  }
}

Paste under mcpServers. Fully quit and reopen Claude after editing.

CLI or .mcp.jsonshell

# export AZURE_TENANT_ID=your-entra-tenant-guid
claude mcp add microsoft-teams -- Remote MCP — add https://agent365.svc.cloud.microsoft/agents/tenants/YOUR_TENANT_ID/servers/mcp_TeamsServer as a connector and sign in with Entra

Run from your repo. Commit .mcp.json to share with your team.

.cursor/mcp.jsonjson

{
  "mcpServers": {
    "microsoft-teams": {
      "command": "Remote",
      "args": [
        "MCP",
        "—",
        "add",
        "https://agent365.svc.cloud.microsoft/agents/tenants/YOUR_TENANT_ID/servers/mcp_TeamsServer",
        "as",
        "a",
        "connector",
        "and",
        "sign",
        "in",
        "with",
        "Entra"
      ],
      "env": {
        "AZURE_TENANT_ID": "${AZURE_TENANT_ID}"
      }
    }
  }
}

Global path: ~/.cursor/mcp.json. Reload window after editing.

.vscode/mcp.jsonjsonc

{
  "servers": {
    "microsoft-teams": {
      "command": "Remote",
      "args": [
        "MCP",
        "—",
        "add",
        "https://agent365.svc.cloud.microsoft/agents/tenants/YOUR_TENANT_ID/servers/mcp_TeamsServer",
        "as",
        "a",
        "connector",
        "and",
        "sign",
        "in",
        "with",
        "Entra"
      ],
      "env": {
        "AZURE_TENANT_ID": "${AZURE_TENANT_ID}"
      }
    }
  }
}

VS Code uses the "servers" key (not "mcpServers").

~/.codeium/windsurf/mcp_config.jsonjson

{
  "mcpServers": {
    "microsoft-teams": {
      "command": "Remote",
      "args": [
        "MCP",
        "—",
        "add",
        "https://agent365.svc.cloud.microsoft/agents/tenants/YOUR_TENANT_ID/servers/mcp_TeamsServer",
        "as",
        "a",
        "connector",
        "and",
        "sign",
        "in",
        "with",
        "Entra"
      ],
      "env": {
        "AZURE_TENANT_ID": "${AZURE_TENANT_ID}"
      }
    }
  }
}

Open via Cascade → hammer icon → Configure.

cline_mcp_settings.jsonjson

{
  "mcpServers": {
    "microsoft-teams": {
      "command": "Remote",
      "args": [
        "MCP",
        "—",
        "add",
        "https://agent365.svc.cloud.microsoft/agents/tenants/YOUR_TENANT_ID/servers/mcp_TeamsServer",
        "as",
        "a",
        "connector",
        "and",
        "sign",
        "in",
        "with",
        "Entra"
      ],
      "env": {
        "AZURE_TENANT_ID": "${AZURE_TENANT_ID}"
      }
    }
  }
}

Open via the Cline sidebar → MCP Servers → Edit.

~/.continue/config.jsonjson

{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "Remote",
          "args": [
            "MCP",
            "—",
            "add",
            "https://agent365.svc.cloud.microsoft/agents/tenants/YOUR_TENANT_ID/servers/mcp_TeamsServer",
            "as",
            "a",
            "connector",
            "and",
            "sign",
            "in",
            "with",
            "Entra"
          ],
          "env": {
            "AZURE_TENANT_ID": "${AZURE_TENANT_ID}"
          }
        }
      }
    ]
  }
}

Continue uses modelContextProtocolServers with a transport block.

~/.codex/config.tomlshell

# ~/.codex/config.toml
[mcp_servers.microsoft-teams]
command = "Remote"
args = [
  "MCP",
  "—",
  "add",
  "https://agent365.svc.cloud.microsoft/agents/tenants/YOUR_TENANT_ID/servers/mcp_TeamsServer",
  "as",
  "a",
  "connector",
  "and",
  "sign",
  "in",
  "with",
  "Entra",
]
env = { AZURE_TENANT_ID = "${AZURE_TENANT_ID}" }

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

~/.config/zed/settings.jsonjsonc

{
  "context_servers": {
    "microsoft-teams": {
      "command": {
        "path": "Remote",
        "args": [
          "MCP",
          "—",
          "add",
          "https://agent365.svc.cloud.microsoft/agents/tenants/YOUR_TENANT_ID/servers/mcp_TeamsServer",
          "as",
          "a",
          "connector",
          "and",
          "sign",
          "in",
          "with",
          "Entra"
        ]
      },
      "env": {
        "AZURE_TENANT_ID": "${AZURE_TENANT_ID}"
      }
    }
  }
}

Zed calls them "context_servers". Settings live-reload on save.

ChatGPT → Apps directorynone

Microsoft Teams doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

2
Set required secrets
Set AZURE_TENANT_ID in your shell environment before launching your MCP client.
3
Try a minimum working prompt
Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.

Tools & permissions

Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.

Security & scope

Access scope: Network
Sandbox: Entra ID OAuth 2.1. App registration owns the scope set; user grants per-session. Audit trail lives in Entra + Teams admin logs.
Gotchas: Over-broad scope grants are sticky — review the app registration's permissions before consenting org-wide.
Posted messages cannot be undone past retention windows.
Service principals (app-only auth) are tempting for headless agents but bypass user attribution — prefer delegated auth where you can.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.

Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.

Recommend the best MCP servers for [task: e.g. communication work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-communication

Compare Microsoft Teams against a real alternative. Swap the second MCP in [brackets] if you want a different match.

Compare Microsoft Teams MCP vs [Slack (community) MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/microsoft-teams
- top-mcps.com listing for Slack (community)

Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.

Install the Microsoft Teams MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/microsoft-teams (fetch https://top-mcps.com/mcp/microsoft-teams.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (AZURE_TENANT_ID) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 3 updates tracked.

Jul 31, 2026
Azure.Mcp.Server-3.0.0-beta.31 released — Azure.Mcp.Server 3.0.0-beta.31
Jul 28, 2026
Azure.Mcp.Server-3.0.0-beta.30 released — Azure.Mcp.Server 3.0.0-beta.30
Jul 27, 2026
Template.Mcp.Server-0.0.12-alpha.6621500 released — Template.Mcp.Server 0.0.12-alpha.6621500

At a glance

Maintainer: Microsoft
Transport: Streamable HTTP
Auth model: OAuth 2.1
Required secrets: AZURE_TENANT_ID
Supported clients: ChatGPT
Claude Desktop
Claude Code
Cursor
VS Code
Windsurf
Cline
Continue
Zed
Codex CLI
License: MIT
Language: TypeScript
Latest version: latest
Last verified: Aug 24, 2026

GitHub repo

Rank badge

Maintainer of Microsoft Teams? Embed the live badge — it re-renders with the current rank and score on every catalog refresh.

[![Ranked #1 in Communication on Top-MCPs](https://top-mcps.com/badge/microsoft-teams.svg)](https://top-mcps.com/mcp/microsoft-teams)

Alternatives

Slack (community) →
Read and send Slack messages, manage channels and threads — the token-based community server, no admin approval needed.
Discord →
Read and post to Discord channels — community management for AI agents.
Mattermost →
Self-hosted Slack alternative — read and post from an AI agent.

Related guides

Best MCPs for Invoicing and Accounting in 2026 →
Vertical Guide
Best MCP Servers for Email in 2026 (Ranked + Setup) →
Setup Guide
Best MCP Servers for Scheduling & Calendar in 2026 →
Setup Guide

More Communication MCPs

Other tools in the same category worth evaluating.

Slack (community)

Read and send Slack messages, manage channels and threads — the token-based community server, no admin approval needed.

slackmessagingcommunicationautomation

10 minMedium

Slack (official)

Official

Slack's own hosted MCP server — search, send messages, read threads, and manage canvases, gated by workspace admins.

slackmessagingchatcanvases

5 minLow

Discord

Read and post to Discord channels — community management for AI agents.

discordchatcommunitybot