No user-submitted related servers found.
Scored across 36 tools
Most tools target clearly distinct resources and actions (CRUD records vs website pages vs translations vs attachments), and the descriptions explicitly separate list_records from search_records. However, several introspection/action helpers overlap—get_model_actions, get_available_actions, and get_model_interface all expose button/action/CRUD data—and fetch_and_upload versus upload_binary both handle local files, creating a few confusing boundaries.
Nearly all names use snake_case with consistent families like list_*, get_*, set_page_*, and translation_*. Minor deviations exist (translation_get/update/audit use noun_verb while most use verb_noun; single verbs create/update/archive), but the conventions remain readable and predictable.
36 tools is well above the 3–15 sweet spot and the 25+ 'too many' threshold, indicating an overloaded surface for one MCP server. Several tools are convenience wrappers or near-duplicates (get_model_interface vs get_model_actions/get_fields, fetch_and_upload vs upload_binary), so not every tool clearly earns its place.
The surface covers CRUD (create/update/archive), read/search/group, actions/buttons, website pages, translations, attachments/binary migration, messaging/activities, and skills/workflows. Gaps exist—no hard delete/unlink operation (archive only), no report rendering/download despite reporting metadata, and no page/menu deletion—but core workflows are well-covered.