Skip to main content
Glama
javidjamae

@ffmpeg-micro/mcp-server

by javidjamae
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to @ffmpeg-micro/mcp-server

No user-submitted related servers found.

    Related Servers

    • Transcodely by transcodely

      Transcodelyofficial

      transcodely
      A
      license
      A
      quality
      A
      maintenance
      Transcodely is agent-native video infrastructure: transcode, host, and get a playable link back from one natural-language prompt. Connect with one OAuth click, then create a job, poll status, and hand back a durable player URL - 7 tools, including AI-generated captions.
      12
      7
      MIT

    • Video & Audio Editing MCP

      misbahsy
      A
      license
      B
      quality
      D
      maintenance
      Provides powerful video and audio editing capabilities through FFmpeg, enabling AI assistants to perform professional-grade operations including format conversion, trimming, overlays, transitions, and advanced audio processing.
      27
      84
      MIT

    • mcp-ffmpeg

      kevinten-ai
      A
      license
      A
      quality
      C
      maintenance
      Provides 30+ FFmpeg video and audio editing tools via MCP, enabling AI assistants to perform operations like trimming, transcoding, overlays, and composition directly.
      27
      4
      MIT

    • ff-toolkit

      inthepond
      A
      license
      A
      quality
      B
      maintenance
      Enables LLMs to perform FFmpeg operations like clipping, merging, extracting audio, adding subtitles, and transcoding videos via a set of tools exposed as an MCP server.
      5
      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

    A3.9/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have distinct purposes: transcode vs transcribe vs upload. The overlap between 'transcode_video' and 'transcode_and_wait' is clarified by description, and 'get_download_url' vs 'get_transcribe_download' are distinguished by resource type. Minor potential confusion between 'get_transcode' and 'get_transcribe' but their names indicate the difference.

    Naming Consistency3/5

    Naming patterns are mixed: 'transcode_video', 'get_transcode', 'list_transcodes', 'cancel_transcode' follow verb_noun, but 'transcode_and_wait' uses a conjunction, and 'get_transcribe_download' breaks the pattern. Also 'request_upload_url' and 'confirm_upload' are not prefixed with 'upload'. Overall inconsistent.

    Tool Count5/5

    11 tools is appropriate for the scope: covers transcode creation, monitoring, cancellation, convenience wrapper; transcribe creation and download; upload flow; and download URL generation. Neither too few nor too many for a focused MCP server.

    Completeness3/5

    The tool set covers core transcode and transcribe workflows but lacks listing and cancellation for transcribe jobs, while these exist for transcode. There is also no delete or update for completed jobs. Minor gaps that could hinder workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources