Related Servers

Most tools map cleanly to a resource+action (content_list vs content_get vs content_delete, db_tables vs db_table vs db_query), and the migration family is well differentiated by lifecycle stage. However there are genuine overlaps: aism_plugin_update duplicates the update behavior described inside aism_plugin_action, and aism_plugin_install vs aism_plugin_upload (and the theme equivalents) require careful reading to choose correctly. aism_migration_export also overlaps conceptually with run/copy, which the description itself has to excuse.

All 42 tools share the aism_ prefix and snake_case, which is highly predictable. Deviations are minor but present: singular/plural mismatch for the same resource (aism_plugin_upload vs aism_plugins_list, aism_theme_install vs aism_themes_list), and several tools drop the verb entirely (aism_revisions, aism_sites, aism_diagnostics, aism_logs) while others use resource_verb ordering (aism_content_list) or verb_resource ordering (aism_discover).

42 tools is heavy, but the server genuinely spans content, media, plugins, themes, users, database, migrations, diagnostics, cron, logs and settings, so most tools earn their place. Still, the surface could be trimmed — the standalone aism_plugin_update is largely redundant with aism_plugin_action, and the upload/install split doubles the plugin and theme surfaces. It sits above the comfortable 3-15 range even for a broad admin domain.

Coverage is unusually broad: content CRUD, media upload, plugin/theme install-activate-update-delete, user review and quarantine/restore, options read/write, read-only SQL, diagnostics, cron, logs and a full multi-site migration lifecycle. Remaining gaps are small but real — no user creation or role editing, and aism_sites can only list connections, with no way to add, update or remove a site connection. Revisions are explicitly read-only, which is a documented limitation rather than a silent hole.