QuillBot Local MCP
Related Servers
Alternatives to QuillBot Local MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to automate a Playwright browser by having an LLM specify step outcomes while a decision model selects elements, actions, values, and statuses, with optional WebMCP tool invocation.730 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables 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.12Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables autonomous web QA by exposing Playwright browser control as MCP tools for navigation, accessibility snapshotting, interaction, and bug detection.0MIT
- AlicenseNot gradedqualityAmaintenanceEnables 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 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables 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 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables 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 npmMIT
TDQS
Scored across 4 tools
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.
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.
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.
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.