Skip to main content
Glama
rexposadas

Attendee MCP Server

by rexposadas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Attendee MCP Server

No user-submitted related servers found.

    Related Servers

    • ChatterBox MCP Server

      ChatterBoxIO
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI agents to join and interact with online meetings (Zoom and Google Meet), capturing transcripts and recordings to generate meeting summaries.
      3
      10
      MIT

    • Google Meet MCP Server

      cool-man-vk
      A
      license
      Not graded
      quality
      F
      maintenance
      The Google Meet MCP Server enables AI agents to create, manage, and retrieve Google Meet meetings. Built on the Model Context Protocol, it exposes tools for scheduling, updating, and deleting meetings, making it easy to integrate Google Meet functionalities
      7 npm
      2
      MIT

    • Teams MCP

      hahsanayub
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server enabling AI assistants to interact with Microsoft Teams, users, chats, and organizational data via Microsoft Graph APIs.
      643 npm
      MIT

    • VoIPBin MCP Server

      nrjchnd
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI models to interact with VoIPBin's VoIP services, supporting features like call management, agent management, campaigns, conferences, and chat functionality.
      4
      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

    Every tool has a clearly distinct purpose focused on specific meeting bot operations. There is no overlap between actions like creating bots, deleting data, getting status/transcripts/recordings, controlling bot speech/chat, or sending media. The descriptions make each tool's unique function immediately apparent.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case throughout. The naming convention is perfectly uniform, using clear action verbs like create, delete, get, make, remove, and send paired with specific nouns describing the operation's target.

    Tool Count5/5

    With 11 tools, the server provides comprehensive coverage for meeting bot management without being overwhelming. This count is well-scoped for the domain, offering a complete set of operations for bot lifecycle, data retrieval, and interaction capabilities.

    Completeness5/5

    The toolset offers complete CRUD/lifecycle coverage for meeting bots: creation, status monitoring, data retrieval (transcripts, recordings, chats), interaction (speaking, messaging, media sharing), and removal/deletion. There are no obvious gaps, and agents can perform all essential meeting bot workflows seamlessly.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources