ms-copilot-mcp
Related Servers
Alternatives to ms-copilot-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceIntegrates Microsoft 365 enterprise data into GitHub Copilot and Claude Desktop using Microsoft 365 Copilot APIs. It enables natural language queries across SharePoint, OneDrive, emails, calendars, and Teams meetings while maintaining full enterprise permission enforcement.510MIT
- AlicenseNot gradedqualityCmaintenanceIntegrates with Microsoft 365 Copilot APIs to enable retrieval of content from SharePoint and OneDrive, document search across M365, and conversational AI interactions with your Microsoft 365 data while respecting access permissions.15 npm19MIT
- FlicenseNot gradedqualityDmaintenanceEnables Microsoft 365 Copilot to interact with Salesforce through REST APIs, supporting queries, object descriptions, pipeline summaries, and anomaly detection.-
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants like Cursor and Claude Desktop to interact with Slack workspaces, allowing message sending, channel reading, user management, and file operations through natural language.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to read messages, threads, channel info, user profiles, search conversations, and generate permalinks in Slack workspaces.1MIT
- AlicenseAqualityBmaintenanceConnects AI assistants to GitHub repositories, pull requests, issues, commits, and code search while enabling repository visibility controls, CI/CD monitoring, sandboxed local filesystem access, and code quality/security analysis.131MIT
TDQS
Scored across 5 tools
Each tool maps to a distinct resource and action: fleet runtime, Slack write/read, GitHub status, and pod health. There is no meaningful overlap between the status-style tools and the Slack communication tools.
All names follow snake_case and use a domain prefix like slack_net, github_repos, or pod_health. The minor inconsistency is that some names use verbs (say, read) while others use nouns (brief, status), but the pattern remains predictable.
Five tools is a well-scoped count for an ops/coordination server. Each tool serves a clear purpose without redundancy or bloat.
The set covers the core monitoring and communication workflows well: fleet status, pod health, repository state, and Slack messaging. It lacks deeper mutation or diagnostic capabilities, but these are not clearly required by the stated purpose.