A
licenseA
qualityC
maintenanceEnables Claude, Cursor, ChatGPT and other AI agents to search and read a Helpjuice knowledge base, draft and update articles, and audit stale content through the Helpjuice API.
12
MIT
libredesk-mcp
by SpaceParrots
Related Servers
Alternatives to libredesk-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables integration with Zendesk to retrieve and manage tickets and comments, analyze tickets, draft responses, and access Help Center articles as a knowledge base.-
- AlicenseAqualityCmaintenanceEnables agents to search, read, list, and amend a git-backed markdown knowledge base, automatically committing and publishing changes.4MIT
- AlicenseBqualityDmaintenanceAllows AI models to interact with SourceSync.ai's knowledge management platform to organize, ingest, retrieve, and search content in knowledge bases.2587 npm3MIT
- FlicenseNot gradedqualityAmaintenanceEnables users to fetch, create, and update Zendesk tickets and comments, analyze tickets and draft responses, and query Help Center articles as a knowledge base.-
- FlicenseNot gradedqualityAmaintenanceEnables operators to retrieve and manage tickets and comments, analyze tickets and draft responses via specialized prompts, and access Help Center articles as a knowledge base.-
TDQS
A3.9/5.0
Scored across 8 tools
Disambiguation4/5
Each tool owns a clear domain (help centers/collections, articles, snippets/FAQ, lookup, publish, delete), and cross-cutting publish/delete operations are separated by intent. The raw request tool overlaps everything, and collection/article lifecycle operations are split across several tools, but the descriptions make the boundaries readable.
Naming Consistency3/5
All names use a consistent libredesk_ snake_case prefix, but the category names mix nouns (help_center, articles, ai_knowledge, lookup, status) and verbs (publish, delete, request). This is readable, but it is not a uniform verb_noun or noun-only pattern.
Tool Count5/5
Eight tools is well within an appropriate range and maps to coherent domains rather than exposing one tool per endpoint. Each bucket earns its place, including lookup, publish/delete separation, and a raw fallback for unsupported operations.
Completeness5/5
The surface covers the full lifecycle for help centers, collections, articles and translations, snippets, FAQ suggestions, and publication/visibility controls. Lookup and raw request provide escape hatches, so there are no obvious dead ends for the apparent knowledge-base and AI-content domain.
Maintenance
ActivityMaintained
ResponsivenessNo issues