Skip to main content
Glama
Sign In
macwhisper-mcp-server

macwhisper-mcp-server

by docdyhr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to macwhisper-mcp-server

No user-submitted related servers found.

    Related Servers

    • Call Recorder MCP

      morganseznec
      A
      license
      A
      quality
      A
      maintenance
      Enables Claude to capture both sides of macOS calls and meetings from apps like WhatsApp, Teams, Zoom, and browsers as aligned microphone and system-audio tracks, then transcribe them locally with Whisper. Supports speaker separation, custom vocabulary, and importing existing audio or video files, with everything processed on-device so no audio leaves the Mac.
      10
      MIT

    • mac-voice-mcp

      jeet0007
      A
      license
      A
      quality
      A
      maintenance
      Enables spoken conversations with Claude on a Mac: Claude speaks through speakers, listens to the user's natural replies, and transcribes them locally. No audio leaves the computer, and it includes tools for voice setup and a hands-free voice mode.
      5
      452 npm
      MIT

    • Raz

      Mateob6
      A
      license
      Not graded
      quality
      C
      maintenance
      Voice interface for Claude Code enabling hands-free, conversational interaction entirely on-device for Apple Silicon Macs. It provides push-to-talk transcription and automatic spoken responses via local AI models.
      MIT

    • meetey

      jej2k5
      A
      license
      Not graded
      quality
      C
      maintenance
      Local-first meeting capture and transcription for Claude Code. Records audio from meeting apps, transcribes locally with whisper.cpp, and produces structured notes via Claude.
      1
      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/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct action: single-file transcription, cancellation, model listing, path listing, and the watch lifecycle (start/stop/results). The watch tools and direct transcription tools have clearly separated purposes with no overlap. An agent can easily tell them apart.

    Naming Consistency5/5

    All seven tools follow a consistent snake_case verb_noun pattern (transcribe_audio, cancel_transcription, list_models, list_allowed_paths, start_watch, stop_watch, get_watch_results). Verb choices are precise and predictable.

    Tool Count5/5

    Seven tools is well-scoped for a focused transcription server. Every tool earns its place: core transcription, lifecycle control, discovery helpers, and the watch-folder feature set.

    Completeness4/5

    Core lifecycle is covered (transcribe, cancel, watch start/stop/results, model and path discovery). Minor gap: there is no status/progress query for an in-flight transcription beyond cancel, but agents can reasonably work around this.

    Maintenance

    ActivityActive
    ResponsivenessSyncing

    Resources