gorelo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUTH_MODE | No | env (default, reads the vars above) or gateway (credentials arrive per-request via X-Gorelo-* headers, injected by the Conduit gateway). | env |
| LOG_LEVEL | No | debug | info (default) | warn | error. | info |
| GORELO_REGION | No | us (default) or au - your account's regional API host. | us |
| MCP_TRANSPORT | No | stdio (default) or http. | stdio |
| GORELO_API_KEY | No | Gorelo Public API key for the tenant. | |
| CONDUIT_S2S_SECRET | No | When set, the HTTP transport requires a valid X-Gateway-S2S header (Conduit sidecar auth) on every /mcp request. |
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 | {} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gorelo_list_ticketsA | List tickets for the service provider, cursor-paginated. Default sort is updatedOn desc. Filter by status, client, priority, type, assignee, contact, tag, group, a keyword query, or a created/updated date range. |
| gorelo_get_ticketC | Get a single ticket by id, with full detail. |
| gorelo_list_ticket_statusesA | List the ticket statuses configured for the service provider. |
| gorelo_list_ticket_tagsA | List the ticket tags configured for the service provider. |
| gorelo_list_ticket_typesA | List the ticket types configured for the service provider. |
| gorelo_list_ticket_commentsA | List the comments on a ticket, cursor-paginated, oldest-first by default. Filter from broadest to narrowest: nothing for every comment, conversationType alone to select a kind, or conversationType with conversationId for one specific conversation. |
| gorelo_get_ticket_commentA | Get a single comment on a ticket. Includes the full BodyHtml (no BodyTruncated flag). |
| gorelo_list_ticket_conversationsA | List the conversations on a ticket. Public/Private (the main thread) come back with a null Id; Side Conversation and Approval carry a real Id usable as conversationId on the comments endpoint. |
| gorelo_get_ticket_approvalA | Get a single approval on a ticket, including its approvers and computed status (Disapproved/Approved/Pending). |
| gorelo_list_clientsB | List clients for the service provider, cursor-paginated, sorted by client id ascending. |
| gorelo_get_clientB | Get a single client by id. |
| gorelo_list_client_locationsB | List the locations for a given client. |
| gorelo_list_contactsA | List contacts for the service provider, cursor-paginated, optionally filtered by client, sorted by contact id ascending. |
| gorelo_get_contactA | Get a single contact by id. |
| gorelo_list_contractsA | List billing contracts, each with the service lines it is made of, cursor-paginated. |
| gorelo_list_assetsA | List agent (managed device) assets for the service provider, cursor-paginated, newest-created first. |
| gorelo_get_assetA | Get a single agent (managed device) asset by id. |
| gorelo_list_custom_assetsA | List custom (non-agent) assets for the service provider, cursor-paginated, newest-created first. |
| gorelo_list_time_entriesA | List logged time across every ticket and task, cursor-paginated, narrowed by any of the filters. |
| gorelo_get_time_entryB | Get a single time entry by id. |
| gorelo_list_billing_rolesA | List the billing roles configured for the service provider. Use a role's id as BillingRoleId when logging time against a ticket. |
| gorelo_list_work_typesA | List the work types configured for the service provider. Use a work type's id as WorkTypeId when logging time against a ticket. |
| gorelo_list_usersA | List users (technicians) for the service provider, cursor-paginated, sorted by user id ascending. |
| gorelo_list_groupsA | List the technician groups configured for the service provider. |
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 24 tools
Each tool targets a distinct resource or action: tickets, comments, conversations, approvals, clients, contacts, contracts, assets, time entries, users, and configuration lists. The list-versus-get pattern is clearly separated, and even related pairs like conversations/comments and assets/custom-assets are distinguishable by their descriptions.
All tools share the gorelo_ prefix and follow a consistent verb_noun convention: list_<resource> for collections and get_<resource> for single entities. Config lists use the same list_<resource> pattern, making the entire tool set predictable.
At 24 tools, the server sits at the heavy end of the typical range. Each tool is straightforward and purposeful, but the overall surface feels large and is made up almost entirely of list/get read operations that could be seen as repetitive.
Read coverage is broad across the main GoRelo entities, but the surface is entirely read-only. There is no ticket update, comment creation, or log-time action, even though billing roles and work types reference logging time, which creates notable workflow gaps for agents that need to act on the data.