Skip to main content
Glama
dockndevai

mcp-teams

by dockndevai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-teams

No user-submitted related servers found.

    Related Servers

    • Teams MCP

      HannahGreco
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to access Microsoft Teams, chats, users, files, and organizational data via Microsoft Graph APIs, including messaging, search, attachment handling, and user management.
      11 npm
      MIT

    • Teams MCP

      Ritchy-EU
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to interact with Microsoft Teams, users, and organizational data via Microsoft Graph APIs, including sending messages, managing chats and channels, and searching messages.
      MIT

    • Teams MCP

      Szymanski61715
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to interact with Microsoft Teams, chats, channels, users, files, and organizational data through Microsoft Graph, including messaging, search, message management, attachments, and authentication.
      11 npm
      MIT

    • Teams MCP

      chenlen45
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to interact with Microsoft Teams and Microsoft Graph APIs for user and team management, channel and chat messaging, message editing and deletion, file upload/download, and advanced message search.
      11 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct Teams entity and action: identity, teams, channels, members, channel messages, replies, and chats. The potentially similar message tools are clearly separated by scope (channel vs. chat vs. reply) and by singular vs. plural retrieval.

    Naming Consistency4/5

    The naming is overwhelmingly consistent with a list_* / get_* verb-noun pattern. The main deviation is whoami, which is a common standard command, and the distinction between list and get is semantically clear.

    Tool Count5/5

    Nine tools is well-scoped for a read-only Microsoft Teams server. Every tool earns its place by covering a distinct read operation without unnecessary redundancy or bloat.

    Completeness4/5

    Core read workflows are covered well: identity, teams, channels, members, channel messages with replies, and chats. The main gaps are the lack of a full get_chat_message equivalent, no search capability, and no write actions, but these are workable for a listing-focused server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources