libredesk-mcp
Related Servers
Alternatives to libredesk-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceExposes the Libredesk customer support REST API as MCP tools, letting an AI assistant read and manage conversations, messages, contacts, notes, agents, teams, tags, macros, views and reports. Writes are enabled by default and can be restricted to read-only GET operations.104MIT
- AlicenseBqualityDmaintenanceAn MCP server that wraps the TeamDynamix (TDX) REST API, enabling AI-assisted IT service management through natural language. It exposes 41 tools for managing tickets, assets, CMDB, knowledge base articles, and other core TDX domains.4185 npm1MIT
- AlicenseAqualityDmaintenanceAn MCP server that exposes the full Gorgias helpdesk API to AI assistants, enabling ticket management, analytics, and customer operations through natural language.10067 npm2MIT
- AlicenseAqualityBmaintenanceMCP server that exposes the i-net HelpDesk Ticket Web-API as tools for AI agents, enabling ticket search, reading, creation, and actions like replying, closing, and escalating, with attachment support.8MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for an AI IT helpdesk that exposes 29 tools, 10 resources, and 6 prompts for ticket management, knowledge base search, employee lookup, reporting, and Slack notifications, with a multi-agent conversation pipeline.-
- FlicenseNot gradedqualityCmaintenanceMCP server that exposes OpenVisio's team collaboration API as 15 tools for AI agents, enabling them to read team state, communicate, and manage tickets autonomously.-
TDQS
Scored across 54 tools
Most tools have distinct resource+action patterns, but there are several conversation retrieval tools (e.g., get_all_conversations, get_assigned_conversations) that could cause confusion if descriptions are not carefully read.
Tool names generally follow a consistent verb_noun pattern in snake_case, though 'update_conversationtags' should be 'update_conversation_tags' and 'media_upload' inverts the usual order, creating minor inconsistencies.
With 54 tools, the count is high but understandable for a full helpdesk platform. It borders on heavy, potentially overwhelming an agent, but each tool corresponds to a distinct operation.
The tool set covers CRUD for agents, contacts, conversations, teams, and statuses, along with search, AI, media, and health—leaving no obvious gaps for the stated domain.