2026-01-21 🧭 Daily News

MCP Directory Passes 500 Servers & First-Party Slack and Teams Integrations Ship

🧭 MCP Public Directory Reaches 500 Active Servers

The Model Context Protocol public server directory has passed 500 actively maintained listings — reaching this milestone just six weeks after the 200-server milestone reported in early January. The acceleration reflects a positive feedback loop: as the MCP ecosystem has grown, the presence of high-quality reference implementations has made it easier for new contributors to build and publish their own servers, compressing the development cycle from the initial 30-minute getting-started guide that Anthropic publishes.

Growth highlights at the 500-server mark

New category leaders — cloud infrastructure (AWS, GCP, Azure management APIs) has emerged as the fastest-growing new category, joining the established developer toolchain and document management clusters
Multi-language server support — the MCP SDK is now officially supported in TypeScript, Python, Go, and Rust, with community-maintained SDKs for Java and C#; the language diversity has broadened the contributor base
Quality ratings — the directory has introduced a community-maintained quality signal based on uptime, documentation completeness, and issue responsiveness, helping users identify well-maintained servers quickly
SDK download milestone — the combined TypeScript and Python MCP SDKs have now been downloaded over 2 million times

🧭 First-Party MCP Integrations for Slack and Microsoft Teams

Anthropic has partnered with Slack and Microsoft to ship first-party MCP servers for both communication platforms. The Slack MCP server and the Microsoft Teams MCP server are published in the official MCP directory and allow Claude deployments to read channel history, search messages, post updates, and retrieve user and channel metadata — all through the standard MCP tool interface. Unlike earlier community-built connectors, the first-party servers are developed and maintained by Anthropic in collaboration with the respective platform teams, with access to official APIs and long-term maintenance commitments.

What the integrations enable

Slack MCP server — channel message retrieval, thread summarisation, search across workspace history, posting messages and replies, and user profile lookup
Microsoft Teams MCP server — team and channel message history, meeting transcript retrieval (for Teams meetings with transcription enabled), posting to channels, and @mention resolution
Enterprise deployment path — both servers support OAuth 2.0 with organisation-level admin consent, enabling IT administrators to deploy the integration at scale without per-user token management