krexel-mcp
Related Servers
Alternatives to krexel-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to deploy static websites to StaticX, including creating sites, uploading builds, publishing releases, and managing domains.62 npmMIT
- AlicenseAqualityDmaintenanceEnables AI agents to deploy, manage, and configure web applications on sota.io, including project creation, deployment, environment variables, custom domains, and rollbacks.1345 npmMIT
- FlicenseBqualityCmaintenanceEnables deploying sites, managing databases, and troubleshooting deployments on Hostwares from AI assistants.14-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to deploy generated files (HTML, PDF, images, etc.) directly to cloud71 hosting, returning a public URL, and manage cloud71 sites via natural language.MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to deploy static websites to the Demox platform with automatic directory packaging and cloud storage integration. It includes tools for managing deployments, such as listing, viewing, and deleting websites.715 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Vercel API for managing projects, deployments, domains, and environment variables.-
TDQS
Scored across 9 tools
Each tool serves a distinct purpose: editing files, getting logs, status, listing deploys, listing files, reading files, rolling back, setting env vars, and shipping sites. No two tools have overlapping responsibilities, making it easy for an agent to select the correct one.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., edit_file, get_logs, list_deploys). Even 'rollback' is a clear single verb. No mixing of conventions or styles.
With 9 tools, the server covers the core deployment lifecycle without being overwhelming. The count is well-scoped for a focused platform like Krexel, allowing efficient agent interaction.
The tool set covers primary deployment operations: create (ship_site, edit_file), read (list_deploys, get_logs, get_status, list_files, read_file), update (edit_file, set_env), and delete (implied via rollback). Minor gaps like explicit env variable listing or deploy deletion are absent but not critical for basic workflows.