No user-submitted related servers found.
Scored across 13 tools
Several tools have overlapping-ish territory: list vs catalog (local records vs account-wide), stop vs power vs remove (three ways to make a deploy 'not running'), and deploy vs expose (two publish paths). The detailed descriptions do clarify the boundaries (e.g. 'prefer power over remove'), but an agent must read carefully to avoid misselection.
All names are single lowercase words, which is at least uniformly styled, but there's no predictable verb/noun convention: some are verbs (list, stop, expose, deploy, rotate) and some are nouns (catalog, project, credentials, status, logs, doctor). Readable but no coherent pattern to infer intent from name alone.
13 tools is a reasonable scope for a deploy/tunnel/workers management server, and most map to distinct lifecycle operations. Slightly heavy with some closely related operations (stop/power/remove), but each earns its place.
Strong lifecycle coverage: deploy, expose, status, logs, stop, remove, power off/on, rotate keys, project filing, credentials, account catalog, and diagnostics. Minor gaps like a bulk redeploy/update-content primitive, but core create-inspect-modify-teardown workflows are all present.
