F
licenseNot graded
qualityD
maintenanceEnables AI agents to edit and serve a static website via natural language, providing file management tools over MCP and HTTP hosting.
-
Staticbot MCP server
by bitfiction
Related Servers
Alternatives to Staticbot MCP server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP-capable agents to create and invoke OpenServerless endpoints, manage secrets, and configure integrations such as S3, PostgreSQL, Redis, Milvus, and MongoDB.13Apache 2.0
Novence MCPofficial
AlicenseAqualityBmaintenanceEnables AI agents to create, check, deploy, and host static sites, manage files and forms, configure custom domains, and view quotas and analytics through a hosted MCP endpoint.2431MIT- AlicenseNot gradedqualityBmaintenanceEnables AI agents to deploy static websites to StaticX, including creating sites, uploading builds, publishing releases, and managing domains.31 npmMIT
@shiplohq/mcpofficial
AlicenseAqualityBmaintenanceEnables AI clients to deploy static sites, track deployments, and manage sites on a Shiplo account through the Model Context Protocol.98 npmMIT- FlicenseAqualityDmaintenanceEnables AI assistants to perform comprehensive SSH operations including command execution, file transfers, port forwarding, and key management through a stateless, Docker-ready MCP server.15-
TDQS
A3.9/5.0
Scored across 63 tools
Disambiguation4/5
Almost every tool targets a distinct resource and action, and the descriptions are detailed enough to separate similar workflows. A few pairs could still be confused, though: get_deployment vs get_migration_deployments, get_auto_deploy_settings vs get_auto_deploy_info, and the deprecated list_github_repositories duplicating list_source_repositories.
Naming Consistency5/5
All tool names follow a consistent snake_case verb_noun pattern, such as list_migrations, create_deployment, retry_sync_run, and choose_frontend_deploy. Even the multi-word actions like push_dns_to_cloudflare and preflight_cloudflare_hosting fit the same predictable style, with no mixed casing or random verb choices.
Tool Count2/5
63 tools is far above the 25+ threshold and would overwhelm an agent even with good organization. The breadth is partly justified by the platform's dual hosting/migration scope, but this surface would be more appropriate split into separate servers for hosting, migrations, sync, and infrastructure management.
Completeness3/5
The core migration, deployment, and sync workflows are deeply covered with create/get/confirm/retry/skip/preview/download operations. However, there are notable lifecycle gaps: no delete or cancel tools for stacks, deployments, templates, migrations, or connected projects, and update operations are limited to auto-deploy settings and sync mode.
Maintenance
ActivityActive
ResponsivenessNo issues