Site Studio
Related Servers
Alternatives to Site Studio
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables external AI agents to edit and manage a self-hosted website via a token-gated MCP server, including page content, data, media, and sandboxed functions with validation and rollback.3Apache 2.0
- AlicenseAqualityDmaintenanceEnables append-only revision projects with SHA-256-fingerprinted changes, style heuristics, human approval checkpoints, and draft-only WordPress export handoffs.9MIT

SitePerto MCPofficial
AlicenseAqualityCmaintenanceEnables AI clients to connect to a selected website via OAuth, send ready-to-use static HTML packages, read and edit text, CSS, and JavaScript with preview, and manage pending updates without automatic publishing.31MIT- FlicenseNot gradedqualityCmaintenanceEnables uploading and serving static websites via MCP tools, with automatic path prefix injection for multi-file sites.-
- AlicenseNot gradedqualityNot gradedmaintenanceEnables clients to select administrator-registered machines and projects, work in isolated Git-versioned sandboxes, inspect diffs, and generate policy-gated publish plans without writing changes back to source.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to manage WordPress content and WooCommerce resources through scoped, expiring connections, with human-approved change proposals, revision checks, audit records, and controlled maintenance windows.GPL 2.0
TDQS
Scored across 16 tools
Most tools target distinct resources and actions, but web_read, web_pages, web_find, and web_css all involve reading related content, and web_screenshot_note/web_preview both return revision info. Descriptions help clarify boundaries, though some overlap remains.
All tools share a 'web_' prefix, but conventions are mixed: some are verbs (web_read, web_find), some are nouns (web_pages, web_css, web_timeline), and some are verb_noun (web_set_text, web_add_page). The inconsistent ordering of web_css_set further breaks the pattern.
16 tools is slightly above the ideal 3-15 range, but the domain is rich (reading, writing, CSS, SVG, checkpoints, preview). Each tool appears to earn its place, so the count is reasonable if a bit heavy.
Core CRUD for nodes and attributes is covered, but several lifecycle operations are missing or only available via the dashboard: undo/redo/restore, checkpoint restore/delete, file-level deletion, and CSS file creation. Agents can work around some gaps, but these are notable omissions for a revision-based editor.