Skip to main content
Glama
ssasuoirafen

teams-mcp-server

by ssasuoirafen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to teams-mcp-server

No user-submitted related servers found.

    Related Servers

    • 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

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

    • 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

      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

    • Teams MCP

      Menon35304
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to interact with Microsoft Teams, chats, files, users, and organizational data through Microsoft Graph APIs, supporting messaging, search, attachment handling, and user management.
      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

    A3.9/5.0

    Scored across 29 tools

    Disambiguation4/5

    Most tools target a distinct resource+action pair and descriptions actively guide selection (e.g. list_channel_messages vs list_thread_replies, send_channel_message vs reply_to_channel_message). The main overlap is create_chat vs send_chat_message, since create_chat is really a send-to-1:1 operation and could be confused with the general chat sender. Otherwise boundaries are clear.

    Naming Consistency5/5

    All 29 tools use a predictable snake_case verb_noun convention (list_*, get_*, send_*, create_*, delete_*, update_*, set_/unset_*, pin_/unpin_*, mark_*). Verb pairs like pin/unpin and set/unset are symmetric and readable. No camelCase or mixed conventions appear.

    Tool Count3/5

    29 tools is on the heavy side for a single server and pushes past the comfortable range, even though Teams is a genuinely broad domain. Each tool is fairly granular (separate read/unread, pin/unpin, set/unset reaction), so consolidation would be possible. The count is borderline rather than clearly wrong.

    Completeness4/5

    The messaging lifecycle is well covered: discovery, reading, sending, replying, editing, deleting, reactions, pins, read state, presence, members and attachment download. Minor gaps exist (edit/delete/reaction on channel thread replies are explicitly unsupported, and file/SharePoint attachments cannot be downloaded), but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources