Skip to main content
Glama

Related Servers

Alternatives to ms-copilot-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Integrates 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.
      5
      10
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Integrates 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 npm
      19
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables Microsoft 365 Copilot to interact with Salesforce through REST APIs, supporting queries, object descriptions, pipeline summaries, and anomaly detection.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables 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.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to read messages, threads, channel info, user profiles, search conversations, and generate permalinks in Slack workspaces.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Connects 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.
      13
      1
      MIT

    TDQS

    A3.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    Five tools is a well-scoped count for an ops/coordination server. Each tool serves a clear purpose without redundancy or bloat.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing