Skip to main content
Glama

Related Servers

Alternatives to Humanizer MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Runs locally on a Mac to give AI clients tools for Mail, Calendar, Reminders, Notes, files and optionally Microsoft Teams, with confirmation required before anything reaches other people. Supports searching, reading, drafting, organizing and writing across these apps while keeping data on the machine.
      MIT
    • F
      license
      A
      quality
      B
      maintenance
      Runs locally on your Mac to give AI agents a shared, private memory of your profile, notes, projects, and saved web pages, with semantic search and version history.
      31
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to edit talking-head videos locally by transcribing footage, applying validated edit operations like cutting fillers and silences, adding zooms, captions, looks and branding, and checking results with rendered previews. Agents can also read pinned editor feedback notes with annotated frames, resolve them, and export MP4, SRT or OTIO while the user watches changes live.
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to see and control your desktop with tools for screenshots, clicks, typing, and more, all locally on macOS and Windows.
      1
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-capable chat clients like ChatGPT, Claude, and Cursor to read, search, edit, and run commands on a local machine, including git operations and browser automation. Runs as a local daemon with workspace path jails, safety modes, checkpoints, and human-in-the-loop approval for edits and shell commands.
      MIT

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools split cleanly along read-only status vs. mutating rewrite, with no overlap in intent or inputs. An agent can pick correctly from the names alone, and the descriptions reinforce the boundary (check readiness first, then submit fields).

    Naming Consistency4/5

    Both names are snake_case and readable, but they use slightly different stems: 'humanizer_status' is a noun-prefixed resource, while 'humanize_copy' is a verb_noun action. It's a minor deviation in an otherwise predictable pair, not a real source of confusion.

    Tool Count3/5

    Two tools is borderline thin, though it matches a narrow single-purpose local service (state check plus one operation). It earns its place, but with only a status probe and one action there is little to compose, so it sits at the low end of well-scoped.

    Completeness3/5

    The core lifecycle (is it ready → rewrite) is covered, but there is no way to cancel a busy run, batch/chunk long inputs despite the ~300-word guidance, or adjust tone/style beyond a plain-vs-markdown format flag. Agents can work around these manually, but the surface has notable gaps for anything beyond a single short call.