No user-submitted related servers found.
Scored across 68 tools
Most tools are scoped to a distinct resource—domains, members, schedules, backups, retention, users—and the plural-list vs singular-action naming helps separate reads from mutations. A few generic status/logs/usage tools overlap in scope, but their descriptions clearly distinguish project status, account usage, platform status, and local runner logs.
All tools share the micro_ prefix and snake_case, and mutations mostly follow a consistent resource_action pattern such as domain_add, member_remove, and backup_restore. Minor deviations like bare-verb tools (doctor, remix, pull, rollback) and noun-only read tools keep it from being perfectly uniform.
68 tools is far beyond the well-scoped 3-15 range and is an extreme surface for a single MCP server, even for a broad platform. This will tax context windows and make tool discovery harder; several status, usage, and billing tools could likely be consolidated.
The surface covers most lifecycle operations across domains, members, invitations, schedules, backups, deployments, users, retention, and platform state, with create/read/update/delete coverage for major resources. Minor gaps remain—no file delete, no product delete/archive, no record create/update—so it is not a perfect 5.