Skip to main content
Glama
Vishnuhh

msteams-personal-mcp

by Vishnuhh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to msteams-personal-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      -

    • msteams-mcp

      hickeroar
      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

    • msteams-mcp

      anielyavuz
      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

    • Teams Messenger MCP App

      imoon
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that bridges Microsoft Teams and MCP-compatible clients, enabling chat integration, message handling, and advanced search capabilities without REST API endpoints.
      1
      -

    • Outlook MCP Server

      doublebash
      A
      license
      Not graded
      quality
      A
      maintenance
      A Model Context Protocol server bridging Claude to Microsoft Outlook + Teams (email, calendar, contacts, tasks, files, Teams meeting recordings + transcripts), deployed on Cloudflare Workers.
      182 npm
      2
      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 29 tools

    Disambiguation4/5

    Tools are largely distinct: read variants (teams_get_messages, teams_get_message, teams_get_unread, teams_get_my_recent_messages, teams_get_mentions) overlap in domain but descriptions clearly differentiate them by scope. Sending/reply/edit/delete and reaction tools have clean, separate purposes, though the sheer number of read tools creates some risk of misselection.

    Naming Consistency4/5

    Consistent teams_ prefix with verb_noun structure (get_messages, send_message, add_reaction, create_group_chat) throughout. Minor deviations like teams_status (noun) and auth verbs (login/logout) break the pattern slightly but remain highly predictable.

    Tool Count3/5

    29 tools is heavy, exceeding the comfortable range, though most earn their place given the breadth of a Teams client (auth, chats, messages, reactions, group admin). A few read variants could be consolidated to trim the surface.

    Completeness4/5

    Covers the core lifecycle well: auth, listing/finding chats, reading/searching messages, sending/replying/editing/deleting, reactions, mentions, unread, files, pinned messages, and group membership management. Gaps exist around sending file attachments and user profiles/presence, but main workflows are complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources