Skip to main content
Glama
imatiach-msft

teams-mcp

by imatiach-msft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to teams-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-teams

      dockndevai
      A
      license
      A
      quality
      A
      maintenance
      Enables agents to read Microsoft Teams data and, with elevated modes, post messages, reply in threads, and send chats via Microsoft Graph, with safe-by-default permission gates.
      9
      41 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

      michal58093
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to interact with Microsoft Teams and Microsoft Graph APIs for user lookup, team and channel messaging, chat management, message search, and file or attachment handling.
      11 npm
      MIT

    • Teams MCP

      salma5718
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to interact with Microsoft Teams and Microsoft Graph APIs for messaging, search, user management, file uploads, and chat/channel operations.
      11 npm
      MIT

    • Teams MCP

      pRorato65
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to interact with Microsoft Teams and Microsoft Graph APIs for messaging, channel and chat management, user lookup, file uploads and downloads, and advanced message search using natural language.
      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.7/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: user info, listing different entities (chats, teams, channels), and sending/retrieving messages for chat vs. channel. The send_via_power_automate tool is uniquely positioned as an alternative delivery mechanism, so no two tools are easily confused.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case (get_, list_, send_), making the set predictable and easy to navigate. The one outlier, send_via_power_automate, still adheres to the same verb-first structure.

    Tool Count5/5

    With 9 tools, the server is well-scoped for a Teams messaging-focused MCP. It provides a solid set of read and send operations without being overbuilt or feeling sparse, fitting comfortably within the ideal 3-15 range.

    Completeness4/5

    The tool surface covers the core lifecycle for messaging: listing entities, reading messages, and sending to both chats and channels. Gaps like updating/deleting messages or creating teams/channels exist, but these are reasonable omissions for a communication-focused server and do not block primary workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources