hatchable-mcp
Related Servers
Alternatives to hatchable-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceMCP server for deploying projects to multiple cloud platforms (Vercel, Railway, Neon, MongoDB Atlas, Docker) and running local dev servers, with orchestration for full-stack deployments.8-
- AlicenseNot gradedqualityCmaintenanceA remote MCP server that lets a coding agent turn a plain-language idea into a real, shareable product — creating the project and data model, serving live API endpoints, deploying custom endpoints and server-side functions, and reading request and function logs. It handles sign-up, OAuth-backed access, and OpenAPI spec generation so people can open, sign into, and use the app the agent builds.MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables Claude to deploy full-stack web apps to Cloudflare, including databases, authentication, and file storage, directly through natural language.-
- AlicenseAqualityBmaintenanceEnables AI agents to build, edit, and publish live websites with hosting, database, auth, and domains via the Model Context Protocol.13191 npm1MIT
- FlicenseNot gradedqualityBmaintenanceA production-grade MCP server for Web3, enabling real-time multi-chain wallet execution, smart contract auto-compilation and deployment, token swaps, and asset hosting via Supabase.1-

thinhost-mcpofficial
AlicenseAqualityCmaintenanceEnables AI agents to publish static sites and build folders as live websites, push updates, provision and manage custom domains with DNS, and send transactional email. Ships as a local pip/uvx server that reads build folders directly, or as a hosted HTTP endpoint for Claude Code, Claude Desktop, and other MCP clients.11MIT
TDQS
Scored across 33 tools
Most tools are clearly distinct (file ops vs. deploy vs. env vs. SQL), but write_file/write_files and get_deployment/list_deployments could cause minor confusion. The descriptions are detailed enough that an agent can usually pick correctly.
The set mostly follows verb_noun (read_file, list_files, create_project, delete_file, set_env), with a few exceptions like deploy, grep, and run_code that are verb-only or noun-verb. Still predictable overall.
33 tools is on the heavy side, but the platform covers a full lifecycle: project management, file editing, database, deploy, env, logs, cron, uploads, and account setup. Each tool has a real purpose, though some could be consolidated.
The surface is remarkably complete for a deployment platform: create/read/update/delete for projects and files, SQL execution, schema inspection, deploy with dry-run, function testing, logs, cron, env vars, uploads, forking, and account setup. No obvious dead ends.