Skip to main content
Glama
KamorionLabs

msteams-local-mcp

by KamorionLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to msteams-local-mcp

No user-submitted related servers found.

    Related Servers

    • zaungast

      mbe24
      A
      license
      A
      quality
      A
      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
      Apache 2.0

    • Telegram MCP

      iamalexzatcepin
      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

    • message-container

      B-HS
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to read and search macOS Messages history through a read-only MCP interface.
      -

    • Teams Messenger MCP App

      aech-ai
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that bridges Microsoft Teams with MCP-compatible clients (LLMs, agentic frameworks, CLI), enabling chat integration, message search, and event streaming without traditional REST API endpoints.
      -

    • Read My ChatGPT

      Async23
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides a read-only MCP server to access ChatGPT conversation history via a local browser process. Allows AI clients to list, get, and search conversations from the authenticated user's ChatGPT account.
      76 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

    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

    ActivitySlowing
    ResponsivenessNo issues

    Resources