Skip to main content
Glama
Sign In
GodModeAI2025

TeamsBridgeMCP

by GodModeAI2025
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to TeamsBridgeMCP

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 Server

      m0nkmaster
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to interact with Microsoft Teams through direct API calls, supporting message search, sending replies, managing favorites, and more without Azure AD registration.
      1,521 npm
      29
      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

    • Teams MCP

      michalparker84
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to interact with Microsoft Teams and Microsoft Graph for messaging, chat and channel operations, user and team discovery, file uploads/downloads, and advanced message search.
      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.5/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct Teams resource and action: chats, channels, messages, meetings, files, and session/auth handling. The closest pairs, list_chats vs list_channels and list_messages vs search_messages, are clearly separated by their descriptions and intended use.

    Naming Consistency4/5

    Most names follow a readable snake_case verb_noun pattern such as list_chats, send_message, upload_file, and search_messages. The main deviation is teams_status and teams_login using a teams_ prefix instead of a verb, but the convention is still mostly predictable.

    Tool Count5/5

    Eleven tools is well within a reasonable range for a Teams bridge and each tool maps to a concrete operation. Auth/status, discovery, messaging, files, and meetings are all represented without excessive fragmentation.

    Completeness4/5

    The surface covers core workflows: listing chats/channels/messages, sending and searching messages, starting chats, transferring files, and listing meetings. Some gaps remain around message edit/delete, channel creation, meeting creation/details, and member listing, but these are workable for the apparent bridge scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources