Skip to main content
Glama
HugoF1234

gilbert-mcp

by HugoF1234
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to gilbert-mcp

No user-submitted related servers found.

    Related Servers

    • tamlil-mcp

      Steven17D
      A
      license
      A
      quality
      B
      maintenance
      Provides read-only access to finished meeting transcripts for AI assistants like Claude Code or Codex, enabling them to answer questions or draft summaries based on the transcriptions.
      4
      3
      Apache 2.0

    • Walkie for MCP

      adamperlis
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to search and read recorded meeting data, including transcripts, notes, action items, and participants, from Walkie's local database.
      1
      MIT

    • Transcript MCP spike

      pratnayake-alphasights
      F
      license
      A
      quality
      C
      maintenance
      Enables LLMs to inspect and search mock transcripts through MCP tools and resources. Supports listing, fetching, and searching transcripts with filters on participants, tags, and content.
      3
      -
    • Vexa by Vexa-ai

      Vexaofficial

      Vexa-ai
      A
      license
      Not graded
      quality
      B
      maintenance
      Open-source meeting bot API with MCP server. Search, retrieve, and analyze meeting transcripts from Google Meet, Zoom, and Microsoft Teams directly from your AI tools.
      3 npm
      2,785
      Apache 2.0
    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

    A4.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a distinct and well-defined purpose: get_meeting returns full details, get_summary returns the summary, get_transcript returns the transcript, list_meetings lists meetings, and search_meetings performs full-text search. There is no overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case (get_*, list_*, search_*). This predictability helps the agent understand the action and resource for each tool.

    Tool Count5/5

    With exactly 5 tools, the set is well-scoped for a meeting retrieval service. Each tool covers a core operation without being too many or too few.

    Completeness3/5

    The tool set is complete for reading and searching meetings, but lacks any write operations (create, update, delete). This is a notable gap for a meeting management server, limiting full lifecycle coverage.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources