elma365-mcp
Related Servers
Alternatives to elma365-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server for managing 1C:Enterprise.Element applications via Console API v2, enabling application listing, deployment with verification, build management, and more.526 PyPI10MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for iiko restaurant management system REST API, providing 39 tools to manage products, employees, entities, documents, payments, reports, and raw API access.1-
- AlicenseAqualityAmaintenanceMCP server for Planfix API enabling task, project, contact, and comment management with 10 tools and 2 skills.2047 npm4MIT
- FlicenseNot gradedqualityDmaintenanceThis MCP server simplifies interaction with the ConnectWise Manage API through API discovery, execution, and a fast memory system for efficient workflows.4 npm-
- AlicenseNot gradedqualityFmaintenanceAn MCP server that provides 36 tools for interacting with the amoCRM (Kommo) API v4, covering leads, contacts, companies, and tasks. It supports full entity lifecycles, account analytics, and bulk operations with integrated OAuth 2.0 and rate limiting.2MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for interacting with Bitrix24 REST API, enabling CRUD operations on deals, contacts, companies, users, leads, and tasks, plus analytics and risk assessment.2-
TDQS
Scored across 9 tools
Each tool targets a distinct resource or action: items, comments, processes, tasks, and users are clearly separated. The pairs like get_users/get_user_by_id and get_comments/add_comment are easily distinguishable as list vs. specific, causing no ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_item, get_tasks, start_process). The verbs are appropriate and the naming is predictable across the entire set.
With 9 tools covering common operations on items, comments, processes, tasks, and users, the count is well-scoped. Each tool serves a distinct purpose without unnecessary duplication or bloat.
The tool surface has significant gaps: items lack get single, update, and delete; comments lack delete; processes lack stop; tasks lack update. These missing operations limit the ability to perform full CRUD or lifecycle management for the domain.