Skip to main content
Glama
hanshengcc

teams-chat-mcp

by hanshengcc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to teams-chat-mcp

No user-submitted related servers found.

    Related Servers

    • teams-reader

      dungpham259dev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to search, read, summarize, and ask about your own Microsoft Teams chats stored locally in SQLite, with tools for listing chats, reading messages, fetching images/links, syncing full history through a logged-in browser session, and suggesting replies. It works with the new Teams macOS cache and does not require Microsoft Graph or admin consent.
      MIT

    • Microsoft 365 remote MCP

      usedrobot
      A
      license
      Not graded
      quality
      C
      maintenance
      Gives Claude access to Microsoft 365 mail, calendar, files, and Teams chat with per-user identity via On-Behalf-Of flow. Supports reading and drafting content, but sending is deliberately disabled.
      25 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

    • msteams-mcp

      anielyavuz
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to read your own Microsoft Teams chats, listing conversations and retrieving chat messages as plain text through Microsoft Graph. It runs locally with delegated, read-only permissions under your own Entra app registration.
      1,521 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 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing conversations, reading messages from one conversation, searching across conversations, drafting a message, and exporting history. There is no overlap in scope or action. An agent can easily select the right tool based on the user's intent.

    Naming Consistency5/5

    All five tools follow a consistent snake_case verb_noun pattern: list_conversations, get_messages, search_messages, draft_message, export_chats. There are no deviations or mixed conventions. The naming is predictable and readable.

    Tool Count5/5

    Five tools is well within the ideal 3–15 range and each tool covers a distinct core operation for a Teams chat assistant. The set is tightly scoped without redundant or filler tools. No obvious missing tool forces an awkward count.

    Completeness4/5

    The surface covers listing, reading, searching, drafting, and exporting chats, which is strong for a read-and-draft focused server. However, there is no programmatic send or reply tool, and no way to fetch conversation metadata or members; these are minor gaps that agents can work around by using draft_message and asking the user to send manually.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources