A
licenseNot graded
qualityC
maintenanceEnables MCP clients to run complete browser workflows through a single run_workflow tool, with anti-detection backends, intelligent element location, automatic retries, and session persistence.
MIT
writ-mcp
Officialby usewrit
Related Servers
Alternatives to writ-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceExposes web search, site mapping, scraping, crawling, schema-validated structured extraction, and stateful Playwright browser interaction as MCP tools, routing every call through the same authenticated REST gateway used by the platform's HTTP clients.1MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for automating Weavy.ai creative workflows. It provides tools to manage projects, add nodes, configure parameters, run generative nodes, and publish workflows via browser automation.5-
- AlicenseAqualityDmaintenanceProvides browser automation, audio transcription, and LLM chat as MCP tools for any agent.7MIT
- AlicenseBqualityDmaintenanceExposes your LLMGraph workflow deployments as MCP tools, allowing AI assistants to invoke them via natural language.129 npmMIT
- FlicenseBqualityDmaintenancePlaywright wrapper for MCP that enables LLM-powered clients to control a browser for automation tasks.4101-
TDQS
A3.7/5.0
Scored across 39 tools
Disambiguation3/5
The core domains (scrape, crawl, browser task, API build, workflows, data, monitors, automation) are mostly distinct and the descriptions use explicit NOT FOR cues. However, several authoring/build/debug tools overlap in practice: writ_website_to_api vs writ_record_website, writ_browser_compose vs writ_browser_act define_function/compose, and writ_create_http_extraction vs writ_update_workflow can be confused, forcing careful reading.
Naming Consistency4/5
All tools use the writ_ snake_case prefix, and most follow a predictable verb_noun pattern (list_workflows, run_workflow, create_monitor, crawl_site). Minor deviations are noun-phrase resources (writ_personas, writ_payment, writ_devices, writ_saved_crawls) and the prepositional writ_website_to_api.
Tool Count2/5
39 tools is very large for an MCP surface; many are sub-actions of longer browser/crawl/workflow workflows that could be grouped. While the platform is broad, the count far exceeds the typical 3-15 well-scoped range and increases selection and context burden.
Completeness4/5
Coverage is strong across scraping, crawling, browser automation, API building, saved workflows, data access, scheduling, monitors, automations, personas and payments. Some lifecycle gaps remain, such as no obvious delete/unwire paths for several resources and monitor listing only indirectly via writ_devices action='monitors', but most gaps are workaroundable.
Maintenance
ActivitySlowing
ResponsivenessNo issues