Skip to main content
Glama
msvargas

meeting-transcriber-mcp

by msvargas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to meeting-transcriber-mcp

No user-submitted related servers found.

    Related Servers

    • digisensus-recorder by Digisensus

      digisensus-recorderofficial

      Digisensus
      A
      license
      Not graded
      quality
      B
      maintenance
      Lets AI agents search, read and export call recordings, transcripts and AI meeting notes from Digisensus Recorder, a free open-source call recorder for macOS, and start or stop recording. Runs locally on the Mac and talks to the app over a Unix socket.
      1
      GPL 3.0

    • ParrotScribe MCP Server

      johanthoren
      A
      license
      A
      quality
      F
      maintenance
      Enables AI agents to interact with the ParrotScribe transcription service on macOS, providing tools to start/stop transcription, retrieve real-time and historical transcripts, and search across sessions.
      8
      9 npm
      MIT

    • voxai-mcp

      Ethan-YS
      F
      license
      Not graded
      quality
      B
      maintenance
      Gives your AI a live, speaker-labeled transcript of the meeting or call happening right now, plus the ability to push advice into the meeting window and speak out loud on the Mac. Requires the VoxAI macOS app — the server reads and writes that app's local files, so tools only return real data on macOS.
      -
    • TypeWhisper MCP by TypeWhisper

      TypeWhisper MCPofficial

      TypeWhisper
      A
      license
      A
      quality
      C
      maintenance
      Connects to the TypeWhisper macOS app to let coding agents transcribe local files, inspect model status, search history, and manage dictionary terms and corrections.
      10
      14 npm
      2
      GPL 3.0

    • Whisper Valet

      yashkotha
      A
      license
      A
      quality
      B
      maintenance
      Enables automated audio restoration, transcription, and speaker diarization via MCP tools for queuing files, monitoring progress, and retrieving speaker-labeled transcripts.
      9
      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

    A4.1/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have clear distinct purposes: the naming cluster (get_naming/confirm_naming/skip_naming) and the watch cluster (set_watch/get_watch_status) are separable, and get_job is unique. transcribe_file vs enqueue_files share the same transcription goal and differ mainly in blocking behavior, which is the one spot an agent could misselect, though descriptions clarify it well.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern (transcribe_file, enqueue_files, get_job, set_watch, get_naming, confirm_naming, skip_naming, get_watch_status). The get_/set_/confirm_/skip_ prefixes are used predictably.

    Tool Count5/5

    Eight tools is well-scoped for a transcription-and-watch domain, with no redundant or filler endpoints. Each tool maps to a distinct capability (sync/async transcription, job polling, naming resolution, watch control and status).

    Completeness4/5

    The surface covers the core lifecycle: submit, queue, poll, resolve naming, and watch automation, and get_job returns transcript results. Minor gaps exist (no job cancellation, no list/enumerate jobs, no speaker enrollment), but the descriptions explicitly flag some of these as intentional and workflows remain achievable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources