Hostsmith MCP Server
Related Servers
Alternatives to Hostsmith MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to deploy and manage static websites hosted in Russia, with features like instant deployment, custom domains, and access control.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to self-host static websites by creating projects, editing files, previewing drafts, and publishing versioned releases with custom domains and a web dashboard.MIT

SnapHostofficial
AlicenseNot gradedqualityBmaintenanceSend a live, private link to a client from Claude. SnapHost publishes what your assistant builds as a shareable website with a stable URL, updates it in place, restricts viewers by email or password, rolls back bad versions, serves custom domains, and stores form and waitlist data with no backend.MIT- AlicenseNot gradedqualityBmaintenanceEnables AI to deploy static sites, search for available domains, and point domains to sites, all without spending money.114 npm3MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to deploy and manage static websites directly through EdgeOne Pages. This self-hosted solution allows for direct file management and website hosting using EdgeOne's infrastructure and KV storage.-
- AlicenseAqualityCmaintenanceInstant web hosting for AI agents. Publish a live site in one call, no account needed.5MIT
TDQS
Scored across 16 tools
Most tools target a distinct resource+action: sites (list/get/create/delete), deploys (files/upload/finalize), and redirects are clearly separated. The only real overlap is among set_redirects, edit_redirects, and add_redirect, which all mutate the same rule list, but the descriptions explicitly differentiate bulk replace, batch edit, and single add.
Every tool is snake_case with a leading verb (list_sites, get_site, create_site, delete_site, add_redirect, test_redirect, etc.), grouped by resource noun. The only slight irregularity is the compound deploy_create_upload, which is still readable and fits the pattern.
16 tools is at the upper edge of the comfortable range but each earns its place across three coherent sub-areas: site lifecycle, deploy pipeline, and redirect management. Slightly heavy on redirect tooling (six tools) relative to the rest.
Site lifecycle (create/list/get/delete), a full two-path deploy pipeline, and complete redirect CRUD plus testing are covered. Gaps exist around site configuration updates (no update_site) and deploy history/rollback, so recovery from a bad deploy means overwriting rather than reverting.