Website Autonomous MCP
Related Servers
Alternatives to Website Autonomous MCP
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceAn MCP server implementing a 7-stage agentic frontend workflow—from design audit to PR review—including AI-driven component generation, browser validation, E2E testing, and CI self-healing.44 npm-

squirrelscanofficial
AlicenseNot gradedqualityAmaintenanceMCP server for website QA auditing, covering SEO, performance, security, accessibility, and agent experience with 260+ rules and AI-optimized output for coding agents.267MIT- AlicenseNot gradedqualityBmaintenanceA production-grade MCP server offering modules for GitHub issue/PR triage, live website auditing, and automated release note generation. It provides robust security features like write-operation confirmation gates, rate limiting, and dual-read storage backends.MIT
- AlicenseNot gradedqualityDmaintenanceA production-oriented MCP server for coding agents that enables multi-project management through secure file operations, Git integration, and safe command execution. It supports project discovery across multiple root directories and provides robust audit logging with both STDIO and HTTP transport options.5 npm2MIT
- FlicenseAqualityDmaintenanceAn MCP server that audits websites for accessibility (WCAG 2.1 AA/EAA), performance, SEO, design quality, and mobile responsiveness, providing actionable scores, grades, and prioritized fixes.6-
- AlicenseCqualityDmaintenanceA production-grade MCP server providing an autonomous AI agent swarm, persistent semantic memory, browser automation, multi-model reasoning, and 78+ tools for AI-first testing and development.63MIT
TDQS
Scored across 78 tools
Multiple tools have overlapping purposes, such as run_accessibility_check versus run_accessibility_audit, or inspect_page versus get_console_errors and get_network_errors. The lack of clear boundaries between generic audit tools and their specific variants makes it hard to select the right tool.
All tool names follow a consistent verb_noun pattern in snake_case, e.g., get_project_summary, create_commit, run_lint, audit_page_seo. The verbs vary (get, run, audit, analyze, generate) but the structure is uniform.
With 78 tools, the server far exceeds the 50+ threshold for extreme mismatch. Even for a broad 'website autonomous' purpose, the tool surface is excessively granular, with many near-duplicate audit/analysis functions.
The tool set covers the full lifecycle from project analysis, git operations, validation, testing, deployment, and extensive auditing (design, accessibility, SEO, performance, conversion, diagnostics). Minor gaps exist, such as lack of an actual rollback tool (only rollback_deployment returns safety status) and no branch listing/deleting, but these are workable.