Skip to main content
Glama
meetstream-ai

MeetStream MCP Server

Official
by meetstream-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to MeetStream MCP Server

No user-submitted related servers found.

    Related Servers

    • AI Workforce MCP Server

      khatrikajal
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides calendar, email, meeting transcription and summarization, and weather tools via MCP, enabling users to manage schedules, handle correspondence, capture meeting insights, and check conditions through natural language.
      MIT

    • eventOS over MCP

      thebobby0x
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes a five-agent event operations fleet as 12 MCP tools, letting any MCP client detect scheduling conflicts, route notifications, brief executives, chase vendor SLAs, enforce GDPR, and design bespoke agent fleets via live LLM calls.
      MIT

    • Grok Bot MCP Bridge

      mozzquito
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to discover and create agents, durably submit messages with verifiable replies, and search source-linked local memory. Exposes eight authenticated tools with owner-approved OAuth, transcript-backed verification, and explicit control over history import and embedding.
      MIT

    • MCP Tool-Calling Agent

      ThePrakashV
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables an LLM to dynamically discover and call tools across multiple MCP servers (file, GitHub, SQL, Python execution) with authentication, rate limiting, and observability, supporting parallel execution and secure deployment.
      -

    • 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
    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 19 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: bot lifecycle (create, status, detail, summary, remove, delete), media/transcript retrieval (transcript, transcriptions, media urls), meeting content (participants, chats, speaker timeline), and live interaction (send chat/image). There is minor overlap between get_bot_status and get_bot_detail, but the difference (current status vs full metadata) is clear.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case: create_bot, get_bot_status, remove_bot, list_transcriptions, send_chat_message, etc. The only slight deviation is webhook_events_guide, but it's still a noun phrase and does not break the overall convention.

    Tool Count4/5

    19 tools is above the typical 3-15 range, but the count is justified by the breadth of features: bot lifecycle, transcripts, media, participants, chat, calendar, and webhook guidance. It feels slightly heavy but each tool covers a distinct function and none are redundant.

    Completeness4/5

    The core meeting bot lifecycle is well covered: create, monitor, retrieve data, leave, delete, and interact. Minor gaps exist—there is no direct tool to create/connect calendar OAuth credentials (only list and schedule against existing connections), and no update/pause/resume bot action—but these can be worked around via the dashboard/CLI or by re-creating a bot.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources