BackCrew GorillaDesk MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GORILLADESK_API_KEY | Yes | Your GorillaDesk API key for authentication |
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 |
|---|---|
| get_companyA | Get the connected company's business info: name, contact details, address, timezone, and office hours. Maps to GET /company. |
| list_usersB | List the company's users (admins and technicians). Maps to GET /users. |
| get_userA | Get a single user's profile: name, role, license, contact info. Maps to GET /users/{userId}. |
| list_customersA | List customers with optional filtering, sorting and pagination. Maps to GET /customers. |
| get_customer | Get a single customer by ID, optionally including their locations and contacts. Maps to GET /customers/{customerId}. |
| create_customerC | Create a new customer with a service location. Maps to POST /customers. |
| update_customerC | Update an existing customer's core details. Maps to PUT /customers/{customerId}. |
| add_customer_noteB | Add a note to a customer's timeline, optionally notifying specific users. Maps to POST /customers/{customerId}/notes. |
| list_phone_typesB | List the phone type labels (e.g. Mobile, Home, Work) available for customer phone numbers. Maps to GET /phone-types. |
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 targets a distinct resource and action: company info, user collection vs single user, customer collection vs create/update, customer notes, and phone type lookup. There is no meaningful overlap or ambiguity between tool purposes.
All tool names follow a consistent lower_snake_case verb_noun pattern, such as list_users, get_user, create_customer, and add_customer_note. The naming clearly signals both the action and the resource, making the set predictable.
Eight tools is a well-scoped size for this server's apparent focus on company, user, and customer data. Each tool has a clear purpose and none feel redundant or unnecessary.
The customer workflow has create, list, and update support but lacks a dedicated get-by-id and delete operation, leaving the customer lifecycle incomplete. Note management is also add-only, and users are read-only, so some common management workflows require external workarounds.