Skip to main content
Glama
Woobox

hatchable-mcp

by Woobox
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to hatchable-mcp

No user-submitted related servers found.

    Related Servers

    • Kleap by kleaphq

      Kleapofficial

      kleaphq
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to build, edit, and publish live websites with hosting, database, auth, and domains via the Model Context Protocol.
      13
      8 npm
      1
      MIT
    • thinhost-mcp by thinhost

      thinhost-mcpofficial

      thinhost
      A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      11
      MIT

    • sitedrop

      t0saki
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for self-hosted static site publishing on Cloudflare Workers. Enables AI coding agents to deploy pages with a single 'publish' tool and get live URLs, with support for atomic updates, versioning, and per-site passwords.
      3 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 33 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources