Website Autonomous MCP
# Website Autonomous MCP
A production-minded MCP server for Rootellect website design and management workflows.
## Features
- Project, brand and store resources
- Protected path policy
- Safe Git task branches and commits
- Validation command tools
- Playwright browser inspection and screenshots
- Vercel preview integration with missing-config safety
- JSONL audit logging
- Stdio and Streamable HTTP transports
## Example workflow
`Redesign the homepage in a premium herbal wellness style. Keep product data, authentication, cart and checkout unchanged. Test mobile and desktop. Create a Vercel preview. Do not deploy to production.`
Call `prepare_website_edit_task`, edit only approved files, then call `finalize_website_edit_task`.
## Version 2
Version 2 adds specialized website audit agents while preserving all Version 1 tools.
New agents:
- `design`
- `seo`
- `performance`
- `accessibility`
- `conversion`
- `diagnostics`
- `landing_page`
Use `run_website_audit` for read-only multi-agent inspection. Use `prepare_multi_agent_edit_task`, `validate_multi_agent_edit`, and `finalize_multi_agent_edit` for controlled edits with before/after screenshots, validation, re-audit, optional Vercel preview, and no production deployment.
See:
- `docs/version-2-agents.md`
- `docs/audit-scoring.md`
- `docs/full-audit-workflow.md`
- `docs/landing-page-agent.md`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.