Skip to main content
Glama
Disneik
by Disneik

Related Servers

Alternatives to QuillBot Local MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables browser automation through MCP with native Playwright operations, deterministic assertions, and natural-language grounded actions, structured extraction, and bounded agent workflows over live page elements.
      12
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables an MCP client to automate a real browser by requesting one outcome at a time, letting a decision model choose each element, action, and value while Playwright executes. Also exposes direct acting, yes/no page checks, question-focused page reading, screenshots, and any tools a page itself registers via WebMCP.
      730 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to automate a real browser by stating one outcome at a time, with a typesafe decision model picking the element, action, and value while Playwright executes it. It also exposes tools for direct actions, yes/no and multiple-choice page checks, focused document reading, screenshots, and calling a page's own WebMCP tools.
      730 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to drive Playwright browser automation through natural-language goals, with Jev/TypeSafe System One deciding targets, actions, values, completion, errors, and irreversible steps. It also exposes tools for checks, page reading, snapshots, screenshots, direct actions, and page-provided WebMCP tools.
      730 npm
      MIT

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: status checks local adapter state, inspect validates visible controls/login readiness, detect runs AI detection, and humanize requests a rewriting proposal. Although status and inspect both relate to integration health, the descriptions cleanly separate them.

    Naming Consistency5/5

    All tools follow the same predictable quillbot_ prefix with lowercase snake_case verbs/nouns: status, inspect, detect, humanize. There are no deviations or mixed conventions.

    Tool Count5/5

    Four tools is well-scoped for a focused local QuillBot adapter. Each tool has a clear role in the workflow: health, validation/login, detection, and humanization.

    Completeness4/5

    The core detection and humanization operations are covered, along with status and integration validation. Minor lifecycle gaps remain, such as explicit session cleanup/logout, batch operations, or configuration tools, but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues