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
      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
      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
    • A
      license
      Not graded
      quality
      B
      maintenance
      A collection of self-hosted, open-source tools that enable AI agents to perform web searching, content crawling, and code analysis tasks like linting and security scanning. It provides power-user capabilities for MCP-compatible clients without requiring external accounts or third-party infrastructure.
      415 PyPI
      5
      MIT

    TDQS

    A4/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have clear, distinct targets: job management (list/wait/cancel), setup inspection, brand kit creation, video checking, and film guide. The only real overlap is make_launch_film versus plan_launch_film + render_launch_film, but the descriptions explicitly clarify the one-shot versus decomposed workflows. An agent should be able to select correctly after reading the descriptions.

    Naming Consistency4/5

    All names are snake_case and mostly follow a verb_noun pattern (list_jobs, make_brand_kit, plan_launch_film, render_launch_film, check_video, wait_for_job, cancel_job). The main deviation is launch_film_guide, which is noun-only rather than verb-led, but it is still readable and predictable.

    Tool Count5/5

    Eleven tools is well within the ideal range and each tool earns its place: three job tools, one setup check, three brand/film planning tools, two film rendering/stills tools, one video checker, and one guide. The decomposition of plan/render is justified by the iterative editing workflow.

    Completeness4/5

    The surface covers the full launch-film lifecycle: brand extraction, planning, rendering, still generation, video quality checks, guidance, and async job control. Minor gaps remain, such as no explicit tool to delete or prune jobs and no tool to read back brand kit outputs other than reading files on disk, but these are workable.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing