RepairDesk MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REPAIRDESK_CONFIG | No | Credential JSON file used when neither credential environment variable is set. | config.json beside server.mjs |
| REPAIRDESK_API_KEY | No | Your RepairDesk API key. Required unless REPAIRDESK_ACCESS_TOKEN or a credential config file is used. | |
| REPAIRDESK_LOG_DIR | No | Where mcp_audit.log is written. An explicit relative path is relative to the process working directory. | logs beside server.mjs |
| REPAIRDESK_BASE_URL | No | Override the RepairDesk API base URL. | https://api.repairdesk.co/api/web/v1 |
| REPAIRDESK_STATE_DIR | No | Shared request pacing/cooldown state directory for server processes. | ~/.cache/repairdesk-mcp |
| REPAIRDESK_TIMEOUT_MS | No | Request and response-body timeout in milliseconds. | 60000 |
| REPAIRDESK_USER_AGENT | No | User-Agent sent on every request. Must not be empty. | RepairDesk-MCP/<version> |
| REPAIRDESK_STATUS_MODE | No | Use API status writes by default. The optional administrator policy value 'web' blocks status writes. | api |
| REPAIRDESK_ACCESS_TOKEN | No | Externally managed OAuth Bearer token. Takes precedence over REPAIRDESK_API_KEY. Required unless REPAIRDESK_API_KEY or a credential config file is used. | |
| REPAIRDESK_UPLOAD_ROOTS | No | Allowed server-side upload directories, separated by the platform path separator. Empty disables uploads. | |
| REPAIRDESK_MIN_INTERVAL_MS | No | Minimum milliseconds between outbound API calls. | 1250 |
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 |
|---|---|
| repairdesk_ticketsB | Search and look up repair tickets. List tickets filtered by status, date, keyword, or tech. Get full details by ticket ID. |
| repairdesk_tickets_writeA | Create/update tickets, add notes, assign techs. WARNING: Status changes may trigger automatic customer SMS/email! Statuses that notify: Repaired, Ready for Pickup, Completed, Waiting on Customer, Waiting For Quote, Cancelled. ALWAYS confirm with user before status changes. |
| repairdesk_customersB | Look up customers by name, phone, email, or ID. |
| repairdesk_invoicesC | Search invoices, get details, or check due/outstanding amounts. |
| repairdesk_inventoryC | Search inventory/parts stock. |
| repairdesk_employeesC | List employees/technicians. |
| repairdesk_shop_infoB | Look up reference data: devices, categories, statuses, colors, networks, tax classes, payment methods, referral sources, repair types, service types, locations, problems (by device), trade-ins, purchase orders. |
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 7 tools
Each tool targets a distinct domain entity (tickets, customers, invoices, inventory, employees, reference data), with read and write operations clearly separated. There is no overlap or ambiguity between tool purposes.
All tools share a consistent 'repairdesk_' prefix and noun-based names (customers, invoices, inventory, etc.). The 'tickets' vs 'tickets_write' pair introduces a minor inconsistency, but overall the naming pattern is predictable and clear.
Seven tools is well-scoped for a repair shop management domain. Each tool covers a necessary function without redundancy, making the set compact and purposeful.
The surface provides full ticket lifecycle (search, create, update), customer lookup, invoice queries, inventory search, employee list, and reference data. Minor gaps like ticket deletion or invoice creation exist, but the core workflows are covered.