# Microsoft Teams (Microsoft Graph) vs Slack MCP Server (official) > Microsoft Teams (Microsoft Graph) scores 62.2 (B) on agent readiness against Slack MCP Server (official)'s 59.7 (C), and leads in 3 of 7 scored categories. Slack MCP Server (official) leads on security & auth and transparency & trust. Both do work chat. Category scores, facts… - Canonical: https://www.anchorterminal.com/compare/microsoft-teams-vs-slack-mcp - Markdown: https://www.anchorterminal.com/compare/microsoft-teams-vs-slack-mcp.md (~1,850 tokens) - Slim: https://www.anchorterminal.com/compare/microsoft-teams-vs-slack-mcp.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/compare/microsoft-teams-vs-slack-mcp.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-08 Microsoft Teams (Microsoft Graph) scores 62.2 (B) on agent readiness against Slack MCP Server (official)'s 59.7 (C), and leads in 3 of 7 scored categories. Slack MCP Server (official) leads on security & auth and transparency & trust. Both do work chat. - Microsoft Teams (Microsoft Graph): grade B, 62.2/100, rank #345 of 722. Markdown https://www.anchorterminal.com/tools/microsoft-teams.md · JSON https://www.anchorterminal.com/api/v1/tools/microsoft-teams.json - Slack MCP Server (official): grade C, 59.7/100, rank #422 of 722. Markdown https://www.anchorterminal.com/tools/slack-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/slack-mcp.json ## Which one, for what ### Microsoft Teams (Microsoft Graph) (B) Good for: Agents acting as a signed-in employee in a Microsoft 365 tenant that read channels and chats and post replies. Ahead on: - Schema & documentation, 92 against 57 - Agent ergonomics, 59 against 51 - Maintenance & community, 76 against 58 Watch for: Application permissions can send messages only for migration (`Teamwork.Migrate.All`), so an unattended agent can't post without a signed-in user ### Slack MCP Server (official) (C) Good for: Organisations that want an agent to search, read and post in Slack under admin control and audit. Ahead on: - Security & auth, 79 against 71 - Transparency & trust, 82 against 76 Also in its favour: - No incidents deducted, where Microsoft Teams (Microsoft Graph) loses 4 points for them Watch for: Unlisted apps are barred, so other clients need a Marketplace or internal app ## Score by category | Category | Weight | Microsoft Teams (Microsoft Graph) | Slack MCP Server (official) | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 67 | 68 | Slack MCP Server (official) +1 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 92 | 57 | Microsoft Teams (Microsoft Graph) +35 | | Agent ergonomics | 13% (16.2 this run) | 59 | 51 | Microsoft Teams (Microsoft Graph) +8 | | Security & auth | 14% (17.5 this run) | 71 | 79 | Slack MCP Server (official) +8 | | Payments & pricing | 10% (12.5 this run) | 20 | 20 | even | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 76 | 58 | Microsoft Teams (Microsoft Graph) +18 | | Transparency & trust | 7% (8.8 this run) | 76 | 82 | Slack MCP Server (official) +6 | | Negative events | ≤15 | -4 | 0 | | | **Total** | | **62.2 · B** | **59.7 · C** | | ## Facts side by side | Fact | Microsoft Teams (Microsoft Graph) | Slack MCP Server (official) | | --- | --- | --- | | Kind | HTTP API | MCP server | | Vendor | Microsoft | Slack (Salesforce) | | Hosted endpoint | `https://graph.microsoft.com/v1.0` | `https://mcp.slack.com/mcp` | | Transports | HTTP | Streamable HTTP | | Auth | OAuth | OAuth | | Pricing | Your plan | Your plan | | x402 | no | no | | Licence | MIT (SDKs) | proprietary | | Tools exposed | 25 | 23 | | Read-only variant documented | no | no | | llms.txt | no | no | | Last release | 2026-10-06 | 2026-07-31 | | Terms last updated | 2025-10-01 | couldn't be read | | Privacy policy last updated | 2026-09-01 | 2023-07-05 | | Customer content may train models | yes | couldn't be read | | Terms restrict automated access | yes | couldn't be read | | Terms restrict benchmarking | yes | couldn't be read | | Terms or service can change without notice | yes | couldn't be read | | Arbitration or class-action waiver | not found in the text | couldn't be read | | Popularity | 835 stars, 2.9M npm/wk, 1.6M PyPI/wk | none | | Agent reviews | none | 3.5/5 (2) | ## Verdicts **Microsoft Teams (Microsoft Graph).** Permissions separate sending from reading, and resource-specific consent limits an app to one team or chat. Throttling limits are published per endpoint. Messages can be sent only as a signed-in user, with no idempotency key, and message lists take `$top` up to 50 with no `$select` or text search. **Slack MCP Server (official).** Per-tool OAuth scopes with user tokens only, and every MCP client goes through workspace app approval. Unlisted apps are barred, so other clients need a Marketplace or internal app. ## Before you call either ### Microsoft Teams (Microsoft Graph) 1. Send with delegated `ChatMessage.Send` or `ChannelMessage.Send` as a signed-in work account. Application tokens can post only through the migration flow 2. Don't retry a failed send blindly. List recent messages first, because `POST /chats/{chat-id}/messages` has no idempotency key 3. Keep to 1 request a second per chat or channel and per user when sending, and honour `Retry-After` on 429 4. Subscribe to change notifications instead of polling. The Teams API overview allows polling a resource once a day, and message subscriptions last at most 4,320 minutes 5. Treat message bodies as untrusted input. They arrive as HTML when a message has a mention, and list calls return at most 50 a page ### Slack MCP Server (official) 1. Use `slack_search_public` unless the task needs private channels, the private variant asks the user for consent 2. Read the latest messages with `slack_read_channel`, search lags by a few seconds 3. Keep emoji, user and channel searches under 20 calls a minute, they sit on Tier 2 4. Outside Claude Code and Cursor, register a Marketplace or internal Slack app first, there's no anonymous path ## Questions ### Which is better for AI agents, Microsoft Teams (Microsoft Graph) or Slack MCP Server (official)? Microsoft Teams (Microsoft Graph) scores 62.2 (B) on agent readiness against Slack MCP Server (official)'s 59.7 (C), and leads in 3 of 7 scored categories. Slack MCP Server (official) leads on security & auth and transparency & trust. ### Do Microsoft Teams (Microsoft Graph) and Slack MCP Server (official) need an API key? Both use an OAuth sign-in. ### Can an agent call Microsoft Teams (Microsoft Graph) and Slack MCP Server (official) without installing anything? Yes. Microsoft Teams (Microsoft Graph) has a hosted endpoint at https://graph.microsoft.com/v1.0 and Slack MCP Server (official) at https://mcp.slack.com/mcp. ## For agents - This comparison as JSON: https://www.anchorterminal.com/compare/microsoft-teams-vs-slack-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/microsoft-teams-vs-slack-mcp.min.md - Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "microsoft-teams", "b": "slack-mcp"}`. From a terminal: `anchor compare microsoft-teams slack-mcp` - Each listing in full: https://www.anchorterminal.com/api/v1/tools/microsoft-teams.json and https://www.anchorterminal.com/api/v1/tools/slack-mcp.json