mcp-daktela
Related Servers
Alternatives to mcp-daktela
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceMCP server that exposes Acronis Cyber Protect Cloud APIs as 14 read-only tools for managing alerts, tasks, agents, resources, policies, and tenants.-
- AlicenseAqualityAmaintenanceA read-only MCP server providing 56 tools to query Qobrix real-estate CRM data, covering listings, leads, viewings, offers, contracts, analytics, and more, with RESO Data Dictionary alignment and caching support.643Apache 2.0
- AlicenseNot gradedqualityAmaintenanceRead-only MCP server for Clockify time tracking, exposing 60 raw read tools and five workflows for status, workspace overview, and review of days/weeks.MIT
- AlicenseBqualityCmaintenanceMCP server for the DataGate billing platform API, providing read-only tools to manage customers, invoices, products, agreements, sites, and payments.13MIT
- AlicenseAqualityCmaintenanceRead-only MCP server for the Action1 RMM REST API, enabling access to endpoints, missing updates, vulnerabilities, installed software, policies, automations, and reports.21Apache 2.0
- AlicenseAqualityCmaintenanceA read-only MCP server for AppDynamics that exposes 12 task-oriented tools to query applications, topology, metrics, snapshots, health rules, anomalies, events, alerting config, analytics events, and dependency maps via OAuth API-client credentials.121MIT
TDQS
Scored across 45 tools
There is meaningful overlap between generic tools (list_activities, get_activity) and channel-specific lists/gets (list_calls, get_call, list_emails, get_email, etc.). The descriptions clarify that channel-specific tools return extra fields, but agents may still be uncertain which to use. scan_calls, list_call_transcripts, and get_call_transcript also overlap in purpose.
The dominant pattern is verb_noun (list_*, get_*, count_*), which is consistent and predictable. A few names deviate stylistically (scan_calls, scan_emails, get_call_transcript, list_call_transcripts, get_ticket_detail), but these are minor and don't undermine the overall pattern.
With 45 tools, the server is heavily weighted by nearly identical channel-specific list/get pairs for activities. This feels excessive for the underlying domain, even for a contact-center platform. The count would be more reasonable if generic activity tools were removed or channel-specific tools were consolidated.
The tool set covers read-only operations for tickets, activities, contacts, accounts, CRM records, campaigns, knowledge base, users, and reference data. However, many entities have list_* but no corresponding get_* (e.g., users, groups, pauses, statuses, templates), and there are no write/update/delete tools at all, which limits the usefulness for management workflows.