libredesk-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LIBREDESK_URL | No | The URL of your LibreDesk instance. Used with LIBREDESK_API_KEY and LIBREDESK_API_SECRET to pass credentials directly instead of using the stored `ldesk login` profile. | |
| LIBREDESK_API_KEY | No | The API key for a LibreDesk agent. Used with LIBREDESK_URL and LIBREDESK_API_SECRET to pass credentials directly instead of using the stored `ldesk login` profile. | |
| LIBREDESK_API_SECRET | No | The API secret for a LibreDesk agent. Used with LIBREDESK_URL and LIBREDESK_API_KEY to pass credentials directly instead of using the stored `ldesk login` profile. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| libredesk_help_centerA | Manage help centers and their collections. Undocumented API. Actions:
|
| libredesk_articlesA | Manage knowledge base articles, written and read as markdown. Undocumented API. Actions:
|
| libredesk_ai_knowledgeA | Manage the snippets AI assistants answer from, and review FAQ suggestions. Undocumented API. Actions:
|
| libredesk_lookupA | Look up ids of agents, teams, inboxes and other settings. Actions:
|
| libredesk_publishA | Change what customers and AI assistants see: publish articles and collections, take help centers online or offline, switch FAQ learning. Undocumented API. Actions:
|
| libredesk_deleteA | Delete help centers, collections, articles and snippets. Deletes cannot be undone. Undocumented API. Actions:
|
| libredesk_requestA | Raw API access for what other tools lack; find the endpoint with catalog first. Actions:
|
| libredesk_statusA | Show the profile in use and whether its server accepts it, as which agent. Call it on auth, profile or connection errors. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
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.
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.
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.
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.