LibreDesk MCP
Related Servers
Alternatives to LibreDesk MCP
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceMCP server that exposes the complete Libredesk REST API (54 endpoints) as tools, enabling natural language management of conversations, contacts, agents, teams, and more for the open-source customer support desk.549 npm4MIT
- AlicenseBqualityCmaintenanceExposes the Gapify (Chatwoot-compatible) customer-support API as MCP tools, letting assistants list and search conversations and contacts, send replies, assign teams, apply labels, and resolve tickets in English or Persian. Write actions carry annotations for client confirmation, and a raw-request tool covers endpoints outside the generated set.11835 npmMIT

FirstReply MCP Serverofficial
AlicenseBqualityCmaintenanceExposes FirstReply customer support operations as MCP tools, enabling AI assistants to browse conversations, draft replies, manage API keys, and access support statistics.841MIT- FlicenseNot gradedqualityCmaintenanceEnables AI agents to securely list, retrieve, and search Freshdesk support tickets through typed read-only MCP tools. It supports API-key authentication, rate-limit handling, safe logging, and an offline fictional demo mode.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to query and operate a help desk and service desk through MCP over HTTP, including tickets, requester communications, internal notes, attachments, stage and SLA history, time entries, clients, requesters, desks, knowledge base, contracts, and billing/satisfaction reports.MIT
- AlicenseNot gradedqualityDmaintenanceExposes the full Chatwoot API as 129 tools for AI assistants, enabling account, contact, conversation, message, inbox, team, report, help center, automation, and custom attribute management, plus exclusive Kanban and scheduled message features.7 npmMIT
TDQS
Scored across 104 tools
Many near-duplicate tools exist: search_conversations vs paginated_search_conversations, search_messages vs paginated_search_messages, get_agents vs get_agents_compact, get_macros/get_macros_compact/search_macros, and multiple conversation-list endpoints. Descriptions add useful caveats, but an agent can easily misselect, especially with update_status vs update_conversation_status.
Most tools follow a verb_noun snake_case pattern, but there are notable exceptions such as update_conversationtags, media_upload, overview_charts, public_help_center_search, health_check, and ai_completion. The mix of noun-first and verb-first conventions reduces predictability.
With 104 tools, the surface is far beyond a well-scoped MCP tool set and mirrors a large REST API endpoint-by-endpoint. Many tools are granular or overlapping variants, creating an extreme selection burden for an agent.
Core helpdesk coverage is broad: contacts, conversations, messages, teams, agents, tags, statuses, macros, automations, views, and reports are largely covered. Gaps remain, such as inboxes only being list/get with no create/update/delete, contact notes lacking update, and help-center tools being public read-only.