Related Servers

The toolset has multiple overlapping boundaries, especially among document listing variants (documents_list, documents_search, documents_search_titles, documents_drafts, documents_viewed) and duplicate star concepts (documents_starred vs stars_list, documents_star vs stars_create). Auth-related tools (auth_info, auth_config, provider_info) and redirect tools (attachments_redirect, file_operations_redirect) also blur together. Agents will frequently struggle to pick the correct tool.

Most tools follow a resource_prefix + action pattern such as documents_create, collections_update, and comments_resolve. However, the set also contains bare noun names like documents_drafts, documents_viewed, collections_documents, groups_memberships, and loop_teams, plus verb-first outliers like ldap_login and loop_post. The overall pattern is recognizable but not consistently applied.

With 110 tools, this server is far over-scoped for a focused document-management MCP. It bundles documents, collections, users, groups, auth, LDAP, Telegram, Loop, sync blocks, database rows, attachments, file operations, subscriptions, and more into one namespace. This creates an unwieldy surface that is expensive for agents to navigate and reason about.

The domain coverage is extensive: documents, collections, users, groups, comments, shares, revisions, subscriptions, attachments, and authentication all have substantial lifecycle operations. Minor gaps exist, such as no permanent document purge, no restore-from-revision, no explicit publish action, and limited database row operations, but core workflows are generally well covered.