Skip to main content
Glama

Related Servers

Alternatives to msteams-local-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      A read-only, offline MCP server for Microsoft Teams that searches chats, reads conversations, and finds people directly from the local on-disk cache with no cloud API.
      6
      388 npm
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Microsoft Teams that lets AI assistants search, message, and manage chats, meetings, files, and contacts using your existing Teams browser login—no app approval or Azure AD registration needed.
      1,521 npm
      2
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients such as Claude, Cursor, and VS Code to work with personal Microsoft Teams accounts at teams.live.com, letting users list chats, read messages, find unread conversations, review recently sent messages, and send messages on request. It can be run locally over stdio or deployed as a remote HTTP server on Cloudflare Workers, with each user signing in through Microsoft's device-code flow.
      29
      1
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Provides read-only access to Telegram chats, allowing AI agents to list chats, read messages, and search within chats via local MCP.
      14
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A self-hosted, read-only MCP server that lets AI assistants read your own Microsoft Teams chats and messages through Microsoft Graph using delegated permissions. It exposes tools for checking authentication status, retrieving your profile, listing chats, and fetching chat messages as plain text.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to read and search macOS Messages history through a read-only MCP interface.
      -

    TDQS

    B3.2/5.0

    Scored across 8 tools

    Disambiguation3/5

    Most tools are distinct, but mentions and unread_messages overlap significantly — both describe '@-mentions' and read/unread state. The descriptions try to disambiguate (unread_messages explicitly warns it's just unread @-mentions), but an agent could easily misselect between them or between recent_messages and read_conversation.

    Naming Consistency3/5

    The naming follows a verb_noun pattern (list_accounts, list_conversations, read_conversation, search_messages). However 'recent_messages', 'mentions', and 'overview' break the pattern by being noun-phrases rather than verb_noun. Also verb choice is inconsistent — 'list', 'read', 'search', 'recent', 'mentions', 'overview'. Mix of verb-led and noun-led names.

    Tool Count4/5

    8 tools is a reasonable, well-scoped count for a Teams-cache read-only server. There are no redundant padding tools. Could arguably be condensed (mentions + unread_messages overlap), but 8 is within a comfortable range.

    Completeness3/5

    The server is read-only covering account listing, conversation listing/reading, searching, recency, mentions/unread, and overview. However there are notable gaps: no way to fetch a single specific message by ID, no filter by sender, no pagination beyond simple 'limit', and no ability to drill into unread across all conversation types beyond mentions. The surface is functional for typical 'what happened' queries but lacks finer-grained access.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues