Skip to main content
Glama

Related Servers

Alternatives to MakersMCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to work with local files — merging, compressing and editing PDFs, converting and resizing images, formatting text and data formats, running calculators, generating QR codes and barcodes, and producing invoices, resumes and other documents. Everything runs privately on the user's own machine with no uploads, accounts or API keys, and outputs can be chained from one tool to the next.
      162
      92 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A local stdio MCP server that enables coding agents to find licensed photos and icons, generate color palettes and simple SVG assets, and preview static web prototypes. It also supports editable agent skills for design and prototype review workflows.
      23
      2
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to inspect, convert, resize, crop, merge, extract and OCR local images, PDFs, audio and video entirely on the user's machine. Modules can be toggled individually, and all operations stay within a sandboxed working folder with atomic writes and no data sent anywhere.
      21
      MIT

    TDQS

    A4.1/5.0

    Scored across 24 tools

    Disambiguation4/5

    Despite 24 tools spanning six kits, the descriptions do heavy lifting: each overlapping pair (caption_video vs make_subtitles, check_video vs check_place_limits, reframe_video vs plan_reframe, make_brand_kit vs make_font_kit, take_screenshots vs make_launch_stills) explicitly names its sibling and says when to use the other instead. The plan/render/make triads for launch films are cleanly separated by their side-effect contract (writes film.json vs renders film.mp4). Minor residual confusion remains between the four checking tools and between the two screenshot tools, which an agent must re-read to select.

    Naming Consistency4/5

    Nearly everything is snake_case verb_noun (take_screenshots, record_demo_video, plan_launch_film, fit_music, cancel_job, list_jobs), which makes scanning predictable. The deviations are noun-first or bare-noun names: launch_film_guide, makersmcp_playbook, and arguably check_setup within the job tool group. These are readable and few, so the pattern holds overall.

    Tool Count4/5

    24 tools is on the heavy side of the ideal band, but the surface is genuinely four-to-five sub-products (brand, fonts, screenshots/demo, launch film, captions, music, reframe) plus job orchestration and diagnostics, and each tool maps to a distinct step rather than duplicating another. The plan/check/inspect variants are optional but earn their place by preventing costly re-renders. It would still benefit from consolidation of the check_* family.

    Completeness4/5

    The lifecycle is well covered: asset acquisition (brand, fonts, screenshots), production (demo, launch film, stills), post (captions, subtitles, music fitting, reframe), verification (three check tools), and job control (start/wait/list/cancel) plus setup diagnostics. The main gap is upstream of captions: no tool produces word-level timings from a video or audio, so a user without a speech-to-text file is a dead end, and there is no generic trim/concat or audio voiceover utility.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues