gorelo-mcp
Summary: This MCP server exposes read-only Gorelo PSA tools for querying and retrieving service-provider data.
Search and retrieve tickets with filters for status, client, priority, type, assignee, contact, tag, group, keyword, and date ranges.
Inspect ticket details, comments, conversations, approvals, statuses, tags, and types.
Browse clients, client locations, and contacts.
View billing contracts, time entries, billing roles, and work types.
List agent-managed assets and custom assets.
List technicians/users and technician groups.
Use cursor/pageSize pagination on supported list endpoints.
The provided schema does not expose create, update, or delete operations.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@gorelo-mcp show me open high-priority tickets"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Gorelo MCP Server
MCP server for Gorelo's PSA (Professional Services Automation) REST API - full Public API coverage (tickets, clients, contacts, assets, billing, projects, documents, alerts, and more) - for AI assistants and the WYRE Conduit gateway.
Authentication
Generate an API key for your Gorelo organization and send it as the X-API-Key header - this server handles that on every request. There is no token exchange.
Related MCP server: TicketAI
Configuration
Copy .env.example and set the variables below.
Env var | Description |
| Gorelo Public API key for stdio and |
|
|
|
|
|
|
| Required to start the HTTP transport. The process logs an error and exits non-zero when this is empty or a known placeholder ( |
| Set to exactly |
| Bind address when a secret is configured. Unset means |
| HTTP port. Defaults to |
| Tool selection; see Tool selection. |
|
|
/health stays unauthenticated, does not call getCredentials(), and does not return the API key. The stdio transport does not use CONDUIT_S2S_SECRET.
HTTP authentication
With MCP_TRANSPORT=http and CONDUIT_S2S_SECRET set, every /mcp request must include X-Gateway-S2S. The value is t=<unix seconds>,v1=<hex hmac-sha256>, where the HMAC is SHA-256 over the literal string t=<unix seconds> using CONDUIT_S2S_SECRET as the key. A missing or invalid header returns 401. The proof is valid for five minutes of clock skew.
In AUTH_MODE=gateway, /mcp also requires X-Gorelo-Api-Key. X-Gorelo-Region is optional; when present it must be exactly us or au, and any other value returns 400. The API key header is the only credential source for the request. A missing key returns 401 and does not fall back to GORELO_API_KEY.
POST /mcp HTTP/1.1
X-Gateway-S2S: t=1710000000,v1=<hmac-sha256 hex of "t=1710000000">
X-Gorelo-Api-Key: <tenant api key>
X-Gorelo-Region: usRequest limits
HTTP request bodies are capped at 256 KiB (262144 bytes). After the
X-Gateway-S2Scheck passes, aContent-Lengthabove the cap returns 413 with a JSON-RPC error; bodies withoutContent-Lengthare capped by the MCP SDK transport. Unauthenticated requests still get 401 first.tools/callarguments are capped at 10,000 elements (every array item and object key at any depth). Larger inputs return anisErrortool result and are never dispatched.
These limits address CVE-2026-111768 / GHSA-46jr-4wx8-v453 (memory exhaustion during validation) and GHSA-f897-62hf-6gxq (no request body / batch cap).
Tools
112 tools, generated at build time from Gorelo's OpenAPI spec (spec/gorelo-openapi.json, fetched 2026-10-20: 117 operations, 5 excluded). Names follow gorelo_<verb>_<noun>. The 24 read tools from earlier releases keep their names; their arguments are unchanged (camelCase filters such as pageSize/statusIds as arrays, and id for the get_client/get_contact/get_asset/get_time_entry tools).
Tiers follow the HTTP method:
Tier | Methods | Count | Annotations | Default |
read | GET | 58 |
| on |
write | POST / PUT / PATCH | 36 |
| on (the gateway gates writes), except billing writes (below) |
destructive | DELETE | 18 |
| off; set |
Write tools marked admin create or change clients, contacts, the item catalog, invoices or payments.
Money is read-only by default: the four billing writes (gorelo_create_invoice, gorelo_create_payment, gorelo_create_item, gorelo_update_item; every non-DELETE write under the Billing tag except time entries) are hidden from tools/list and refused at call time unless GORELO_ENABLE_BILLING_WRITES=true. The readonly preset hides them regardless. Billing DELETEs are ordinary destructive tools. Time entry create/update are unaffected.
The machine-readable classification (read / write / destructive / admin / billing_write / excluded_binary / excluded_sensitive) comes from node scripts/generate-tools.mjs --tiers <file>.
Request bodies are passed under a single body argument (the JSON object Gorelo documents for that endpoint). Multi-value filters (statusIds, clientIds, ...) take an array, which is sent comma-joined.
Alerts
Tool | Tier | Description |
| read | Lists alerts in Gorelo across all your clients. |
| write | Raises a new alert against one of your clients in Gorelo, such as an alert from an outside monitoring tool. |
Assets
Tool | Tier | Description |
| read | Gets a single agent (managed device) asset by id. |
| read | Gets a single custom asset by id. |
| read | Gets a single uptime check by id. |
| read | Lists agent (managed device) assets for the service provider using cursor pagination. Results are sorted by createdOn descending (newest first). |
| read | Lists the hardware types a custom asset can be given. |
| read | Lists custom (non-agent) assets for the service provider using cursor pagination. Results are sorted by createdOn descending (newest first). |
| read | Lists uptime checks for the service provider using cursor pagination. Results are sorted by createdOn descending (newest first). |
| write | Creates a custom asset, meaning a device without the Gorelo agent, such as a printer or firewall. Use gorelo_list_custom_asset_hardware_types for valid hardware types. |
| write | Creates an uptime check that pings a host, requests a web address or connects to a TCP port on a schedule. |
| write | Updates a custom asset. Send only the fields you want to change. |
| write | Updates an uptime check. Send only the fields you want to change. |
| destructive | Deletes a managed device (agent asset) from Gorelo. This is destructive and can't be undone from Conduit. |
| destructive | Deletes a custom asset from Gorelo. This is destructive and can't be undone from Conduit. |
| destructive | Deletes an uptime check, which stops that monitoring. This is destructive and can't be undone from Conduit. |
Billing
Tool | Tier | Description |
| read | Gets one contract, including the products and labor in each service line. |
| read | Gets one invoice, with its attachments and line items. |
| read | Gets one catalog item (a product or a bundle) by ID. |
| read | Gets a single time entry by id. |
| read | Lists the billing roles configured for the service provider. Use a role's Id as BillingRoleId when logging time against a ticket. |
| read | Lists billing contracts, each with the service lines it is made of. |
| read | Lists the service provider's invoices, filtered and sorted. |
| read | Lists the categories products are organised under, each with its subcategories. |
| read | Lists the service provider's item catalog: products and bundles. |
| read | Lists the tax rates configured for the service provider. |
| read | Lists logged time across every ticket and task, narrowed by any of the filters. |
| read | Lists the work types configured for the service provider. Use a work type's Id as WorkTypeId when logging time against a ticket. |
| write (admin, billing) | Raises a manual invoice against a client, with line items. |
| write (admin, billing) | Creates a product or a bundle in the item catalog. |
| write (admin, billing) | Records a payment received outside Gorelo against an approved invoice. |
| write | Logs time against a ticket. |
| write (admin, billing) | Partially updates an item. Send only the fields you want to change. |
| write | Partially updates a time entry. Send only the fields you want to change. |
| destructive | Deletes a billing contract from Gorelo. This is destructive and can't be undone from Conduit. |
| destructive | Deletes or voids an invoice, depending on its status. This is destructive and can't be undone from Conduit. |
| destructive | Deletes a product or bundle from the item catalog. This is destructive and can't be undone from Conduit. |
| destructive | Deletes a payment that was recorded through the Gorelo API, for example with gorelo_create_payment. This is destructive and can't be undone from Conduit. |
| destructive | Deletes a logged time entry. This is destructive and can't be undone from Conduit. |
Clients
Tool | Tier | Description |
| read | Gets a single client by id. |
| read | Lists the locations for a given client. |
| read | Lists clients for the service provider using cursor pagination. Results are sorted by client id ascending (oldest first). |
| write (admin) | Creates a client (and its default location) for the service provider. |
| write (admin) | Updates an existing client. Only supplied (non-null) fields are changed. |
| destructive | Deletes a client from Gorelo. This is destructive and can't be undone from Conduit. |
Contacts
Tool | Tier | Description |
| read | Gets a single contact by id. |
| read | Lists contacts for the service provider using cursor pagination, optionally filtered by client. Results are sorted by contact id ascending (oldest first). |
| write (admin) | Creates a contact under a client, or a temporary contact when no client is given. |
| write (admin) | Updates a contact. Send only the fields you want to change. |
| destructive | Deletes a contact from Gorelo. This is destructive and can't be undone from Conduit. |
Deletions
Tool | Tier | Description |
| read | Lists records that have been deleted, so a copy kept in sync through this API can remove them. Results are sorted by DeletedOn ascending, then type id, then id, using cursor pagination. |
Documents
Tool | Tier | Description |
| read | Gets a single document. |
| read | Gets one version of a document, with its body and attachments. |
| read | Lists the records a document is related to. |
| read | Lists a document's versions, newest first. |
| read | Lists the service provider's documents. |
| write | Creates a document with an HTML body, either for a client or for internal use, optionally nested under another document. |
| write | Relates a document to other records. |
| write | Makes a copy of a document as a new document. |
| write | Makes an earlier version the current one. |
| write | Updates a document's title, body or placement. Send only the fields you want to change. |
| destructive | Removes one related item from a document. |
Forms
Tool | Tier | Description |
| read | Lists a form's submitted responses, newest first. |
| read | Lists the service provider's forms, most recently updated first. |
| write | Creates a link someone can use to fill in and submit this form. |
Organization
Tool | Tier | Description |
| read | Lists your Gorelo API keys, newest first. Shows names and details only, never the key values. |
| read | Lists the technician groups configured for the service provider. |
| read | Lists users (technicians) for the service provider using cursor pagination. Results are sorted by user id ascending (oldest first). |
Projects
Tool | Tier | Description |
| read | Gets a single project. |
| read | Returns one comment on a project. |
| read | Returns one task in full. |
| read | Gets one approval on a task, with its approvers. |
| read | Returns one comment on a task. |
| read | Returns a project's comments, newest first. |
| read | Lists a project's sections. |
| read | Lists the project tags configured for the service provider. |
| read | Returns a task's comments, newest first. |
| read | Lists the conversations on a task. |
| read | Lists a project's tasks. |
| read | Lists the project types configured for the service provider. |
| read | Lists projects, newest activity first. |
| write | Creates a project in Gorelo. |
| write | Posts a comment on a project. |
| write | Adds a section to a project. |
| write | Creates a task on a project's board. |
| write | Asks contacts to approve something on a task. |
| write | Posts a comment on a task. |
| write | Starts a side conversation on a task. |
| write | Updates a project. Send only the fields you want to change. |
| write | Updates a section's title or colour. Send only the fields you want to change. |
| write | Updates a task. Send only the fields you want to change. |
| destructive | Deletes a project and every task in it. This is destructive and can't be undone from Conduit. |
| destructive | Deletes one comment on a project. This is destructive and can't be undone from Conduit. |
| destructive | Deletes a project section and every task in it. This is destructive and can't be undone from Conduit. |
| destructive | Deletes a project task. This is destructive and can't be undone from Conduit. |
| destructive | Deletes one comment on a task. This is destructive and can't be undone from Conduit. |
Tickets
Tool | Tier | Description |
| read | Gets a single ticket. |
| read | Gets a single approval on a ticket, with its approvers. This is where approval status lives — the conversations list stays lean and does not carry it. |
| read | Gets a single comment on a ticket. Same shape as a comments-list item except that the full BodyHtml is always included, so there is no BodyTruncated field. |
| read | Lists the comments on a ticket using cursor pagination. Comments read oldest-first by default, like a conversation top to bottom. |
| read | Lists the conversations on a ticket. |
| read | Lists the ticket statuses configured for the service provider. |
| read | Lists the ticket tags configured for the service provider. |
| read | Lists the ticket types configured for the service provider. |
| read | Lists tickets for the service provider using cursor pagination. Default sort is updatedOn desc. |
| write | Creates a ticket in Gorelo. |
| write | Creates an approval on a ticket. Every listed contact starts Pending. |
| write | Adds a comment to a ticket. Gorelo shows it as posted by the API, not by you, and To and Cc come from the ticket's conversation. |
| write | Creates a side conversation on a ticket. Post a comment into it afterward using this conversation's returned Id as conversationId with conversationType=3. |
| write | Partially updates a ticket. Send only the fields you want to change. |
| destructive | Deletes a ticket and its time entries. This is destructive and can't be undone from Conduit. |
| destructive | Deletes a private comment from a ticket. This is destructive and can't be undone from Conduit. |
tools/list size
Measured as the JSON size of the tools/list result (names, descriptions, input schemas, annotations):
Configuration | Tools | Bytes |
| 58 | 39,718 |
default (read + write, no billing writes) | 90 | 87,530 |
| 112 | 102,064 |
Use a preset or GORELO_TOOLS_INCLUDE to shrink the list for clients with tight context budgets.
Tool selection
Env var | Description |
|
|
|
|
|
|
| Comma-separated name globs ( |
| Comma-separated name globs; drop matching tools. |
Presets and filters only narrow the set. A tool hidden from tools/list is also refused if called by name. Selection that leaves zero tools refuses to start.
Exclusions
Five operations are deliberately not exposed. Three because the Conduit gateway has no confirmed binary tool-result or upload path:
Operation | Reason |
| multipart file upload |
| returns a binary PDF |
| returns a binary PDF |
The list lives in EXCLUDED_BINARY in scripts/generate-tools.mjs.
Two more are never exposed under any configuration: POST /v1/api-keys and DELETE /v1/api-keys/{apiKeyId} (EXCLUDED_SENSITIVE; credential minting/revocation is out of scope for an AI tool surface). gorelo_list_api_keys stays: it returns key metadata only (id, name, scopes, dates), never the key value.
Behavior
One generic executor runs every tool: path parameters are URL-encoded, the host is always the region's fixed base URL (
us/au), and redirects are refused.HTTP 429 is retried up to 3 times (honoring
Retry-After, capped at 15s, else exponential backoff).Responses over 100KB are truncated with an explicit
[TRUNCATED: ...]marker; narrow with filters orpageSizeand follow the cursor.403 returns
The Gorelo API key for this connection doesn't have permission to run <tool> (HTTP 403). An admin can check the key's permissions in Gorelo under Settings → Integrations.401, 404 and 422 have their own messages. The API key is never included in errors or logs.
Regenerating
npm run generate # rewrite src/generated/tools.ts from spec/gorelo-openapi.json
npm run generate:check # exit 1 if the committed file is stale (also enforced by a test and CI)To pick up a new Gorelo API version, replace spec/gorelo-openapi.json, run npm run generate, review the diff (new operations need no code unless they use a body format other than JSON, which the generator rejects loudly), and commit both files.
Attribution
The operation-to-tool approach, retry/backoff and size-guard logic are adapted from peetinc/gorelo-mcp-all (MIT, Copyright (c) 2026 peetinc). See THIRD_PARTY_NOTICES.md.
Development
npm install
npm run generate # only after changing spec/gorelo-openapi.json
npm run build
npm test
npm run lint # tsc --noEmitDocker
The image listens on 0.0.0.0 inside the container (MCP_HTTP_HOST) and defaults to AUTH_MODE=gateway. Publish the port on loopback and pass a real S2S secret. In gateway mode, the Gorelo API key arrives on each request as X-Gorelo-Api-Key; it is not read from the environment. Do not pass a known placeholder such as your-s2s-secret or changeme. Startup treats those as unset and exits.
docker build -t gorelo-mcp .
docker run \
-e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \
-p 127.0.0.1:8080:8080 \
gorelo-mcpCompose refuses to start when CONDUIT_S2S_SECRET is unset, sets AUTH_MODE=gateway, does not pass GORELO_API_KEY, and publishes 127.0.0.1:8080:8080. A project .env is interpolation only. Do not add env_file to the gateway service.
CONDUIT_S2S_SECRET="$(openssl rand -hex 32)" docker compose upSingle-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses GORELO_API_KEY:
docker run \
-e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \
-e AUTH_MODE=env \
-e GORELO_API_KEY=your-value \
-e GORELO_REGION=us \
-p 127.0.0.1:8080:8080 \
gorelo-mcpLocal HTTP without a secret is development-only. It binds 127.0.0.1 even if MCP_HTTP_HOST is 0.0.0.0, and logs a warning:
MCP_TRANSPORT=http MCP_ALLOW_INSECURE_DEV=1 npm run start:httpAvailable Tools
90 toolsgorelo_create_alertB
Raises a new alert against one of your clients in Gorelo, such as an alert from an outside monitoring tool.
Inputs: body (required).
gorelo_create_clientB
Creates a client (and its default location) for the service provider.
Inputs: body (required).
gorelo_create_contactA
Creates a contact under a client, or a temporary contact when no client is given.
Inputs: body (required).
gorelo_create_custom_assetA
Creates a custom asset, meaning a device without the Gorelo agent, such as a printer or firewall. Use gorelo_list_custom_asset_hardware_types for valid hardware types.
Inputs: body (required).
gorelo_create_documentA
Creates a document with an HTML body, either for a client or for internal use, optionally nested under another document.
Inputs: body (required).
gorelo_create_form_submission_linkB
Creates a link someone can use to fill in and submit this form.
Inputs: body (required), formId (required).
gorelo_create_projectC
Creates a project in Gorelo.
Inputs: body (required).
gorelo_create_project_commentC
Posts a comment on a project.
Inputs: body (required), projectId (required).
gorelo_create_project_sectionC
Adds a section to a project.
Inputs: body (required), projectId (required).
gorelo_create_project_taskC
Creates a task on a project's board.
Inputs: body (required), projectId (required).
gorelo_create_project_task_approvalB
Asks contacts to approve something on a task.
Inputs: body (required), taskId (required), projectId (required).
gorelo_create_project_task_commentC
Posts a comment on a task.
Inputs: body (required), taskId (required), projectId (required).
gorelo_create_project_task_side_conversationC
Starts a side conversation on a task.
Inputs: body (required), taskId (required), projectId (required).
gorelo_create_ticketC
Creates a ticket in Gorelo.
Inputs: body (required).
gorelo_create_ticket_approvalB
Creates an approval on a ticket. Every listed contact starts Pending.
Inputs: body (required), ticketId (required).
gorelo_create_ticket_commentA
Adds a comment to a ticket. Gorelo shows it as posted by the API, not by you, and To and Cc come from the ticket's conversation.
Inputs: body (required), ticketId (required).
gorelo_create_ticket_side_conversationA
Creates a side conversation on a ticket. Post a comment into it afterward using this conversation's returned Id as conversationId with conversationType=3.
Inputs: body (required), ticketId (required).
gorelo_create_time_entryC
Logs time against a ticket.
Inputs: body (required).
gorelo_create_uptime_checkB
Creates an uptime check that pings a host, requests a web address or connects to a TCP port on a schedule.
Inputs: body (required).
gorelo_duplicate_documentC
Makes a copy of a document as a new document.
Inputs: body (required), documentId (required).
gorelo_get_assetBRead-only
Gets a single agent (managed device) asset by id.
Inputs: id (required).
gorelo_get_clientBRead-only
Gets a single client by id.
Inputs: id (required).
gorelo_get_contactCRead-only
Gets a single contact by id.
Inputs: id (required).
gorelo_get_contractARead-only
Gets one contract, including the products and labor in each service line.
Inputs: contractId (required).
gorelo_get_custom_assetBRead-only
Gets a single custom asset by id.
Inputs: customAssetId (required).
gorelo_get_documentCRead-only
Gets a single document.
Inputs: documentId (required).
gorelo_get_document_versionBRead-only
Gets one version of a document, with its body and attachments.
Inputs: versionId (required), documentId (required).
gorelo_get_invoiceARead-only
Gets one invoice, with its attachments and line items.
Inputs: invoiceId (required).
gorelo_get_itemARead-only
Gets one catalog item (a product or a bundle) by ID.
Inputs: itemId (required).
gorelo_get_projectCRead-only
Gets a single project.
Inputs: projectId (required).
gorelo_get_project_commentCRead-only
Returns one comment on a project.
Inputs: commentId (required), projectId (required).
gorelo_get_project_taskCRead-only
Returns one task in full.
Inputs: taskId (required), projectId (required).
gorelo_get_project_task_approvalBRead-only
Gets one approval on a task, with its approvers.
Inputs: taskId (required), projectId (required), approvalId (required).
gorelo_get_project_task_commentCRead-only
Returns one comment on a task.
Inputs: taskId (required), commentId (required), projectId (required).
gorelo_get_ticketCRead-only
Gets a single ticket.
Inputs: ticketId (required).
gorelo_get_ticket_approvalARead-only
Gets a single approval on a ticket, with its approvers. This is where approval status lives — the conversations list stays lean and does not carry it.
Inputs: ticketId (required), approvalId (required).
gorelo_get_ticket_commentARead-only
Gets a single comment on a ticket. Same shape as a comments-list item except that the full BodyHtml is always included, so there is no BodyTruncated field.
Inputs: ticketId (required), commentId (required).
gorelo_get_time_entryBRead-only
Gets a single time entry by id.
Inputs: id (required).
gorelo_get_uptime_checkBRead-only
Gets a single uptime check by id.
Inputs: checkId (required).
gorelo_list_alertsCRead-only
Lists alerts in Gorelo across all your clients.
Inputs: cursor, typeIds, pageSize, clientIds, +5 more.
gorelo_list_api_keysARead-only
Lists your Gorelo API keys, newest first. Shows names and details only, never the key values.
Inputs: cursor, pageSize.
gorelo_list_assetsARead-only
Lists agent (managed device) assets for the service provider using cursor pagination. Results are sorted by createdOn descending (newest first).
Inputs: query, cursor, pageSize, clientIds, +5 more.
gorelo_list_billing_rolesARead-only
Lists the billing roles configured for the service provider. Use a role's Id as BillingRoleId when logging time against a ticket.
Inputs: no named parameters.
gorelo_list_client_locationsCRead-only
Lists the locations for a given client.
Inputs: clientId (required).
gorelo_list_clientsARead-only
Lists clients for the service provider using cursor pagination. Results are sorted by client id ascending (oldest first).
Inputs: query, cursor, pageSize, statusIds, +4 more.
gorelo_list_contactsARead-only
Lists contacts for the service provider using cursor pagination, optionally filtered by client. Results are sorted by contact id ascending (oldest first).
Inputs: query, cursor, clientId, pageSize, +6 more.
gorelo_list_contractsBRead-only
Lists billing contracts, each with the service lines it is made of.
Inputs: cursor, pageSize, clientIds, statusIds.
gorelo_list_custom_asset_hardware_typesBRead-only
Lists the hardware types a custom asset can be given.
Inputs: no named parameters.
gorelo_list_custom_assetsARead-only
Lists custom (non-agent) assets for the service provider using cursor pagination. Results are sorted by createdOn descending (newest first).
Inputs: query, cursor, pageSize, clientIds, +4 more.
gorelo_list_deletionsARead-only
Lists records that have been deleted, so a copy kept in sync through this API can remove them. Results are sorted by DeletedOn ascending, then type id, then id, using cursor pagination.
Inputs: typeIds (required), since, cursor, pageSize.
gorelo_list_documentsCRead-only
Lists the service provider's documents.
Inputs: query, cursor, sortBy, pageSize, +12 more.
gorelo_list_document_versionsBRead-only
Lists a document's versions, newest first.
Inputs: documentId (required), cursor, pageSize.
gorelo_list_form_responsesBRead-only
Lists a form's submitted responses, newest first.
Inputs: formId (required), cursor, pageSize.
gorelo_list_formsBRead-only
Lists the service provider's forms, most recently updated first.
Inputs: query, cursor, tagIds, groupIds, +5 more.
gorelo_list_groupsBRead-only
Lists the technician groups configured for the service provider.
Inputs: no named parameters.
gorelo_list_invoicesCRead-only
Lists the service provider's invoices, filtered and sorted.
Inputs: query, cursor, number, sortBy, +14 more.
gorelo_list_item_categoriesARead-only
Lists the categories products are organised under, each with its subcategories.
Inputs: no named parameters.
gorelo_list_itemsBRead-only
Lists the service provider's item catalog: products and bundles.
Inputs: skus, query, cursor, typeIds, +11 more.
gorelo_list_project_commentsBRead-only
Returns a project's comments, newest first.
Inputs: projectId (required), cursor, pageSize, sortOrder.
gorelo_list_projectsCRead-only
Lists projects, newest activity first.
Inputs: query, cursor, sortBy, tagIds, +13 more.
gorelo_list_project_sectionsCRead-only
Lists a project's sections.
Inputs: projectId (required).
gorelo_list_project_tagsARead-only
Lists the project tags configured for the service provider.
Inputs: no named parameters.
gorelo_list_project_task_commentsBRead-only
Returns a task's comments, newest first.
Inputs: taskId (required), projectId (required), cursor, sortBy, +4 more.
gorelo_list_project_task_conversationsBRead-only
Lists the conversations on a task.
Inputs: taskId (required), projectId (required).
gorelo_list_project_tasksCRead-only
Lists a project's tasks.
Inputs: projectId (required), cursor, sortBy, dueAfter, +8 more.
gorelo_list_project_typesBRead-only
Lists the project types configured for the service provider.
Inputs: no named parameters.
gorelo_list_taxesBRead-only
Lists the tax rates configured for the service provider.
Inputs: no named parameters.
gorelo_list_ticket_commentsBRead-only
Lists the comments on a ticket using cursor pagination. Comments read oldest-first by default, like a conversation top to bottom.
Inputs: ticketId (required), cursor, sortBy, pageSize, +3 more.
gorelo_list_ticket_conversationsCRead-only
Lists the conversations on a ticket.
Inputs: ticketId (required).
gorelo_list_ticketsARead-only
Lists tickets for the service provider using cursor pagination. Default sort is updatedOn desc.
Inputs: query, cursor, sortBy, tagIds, +13 more.
gorelo_list_ticket_statusesARead-only
Lists the ticket statuses configured for the service provider.
Inputs: no named parameters.
gorelo_list_ticket_tagsARead-only
Lists the ticket tags configured for the service provider.
Inputs: no named parameters.
gorelo_list_ticket_typesBRead-only
Lists the ticket types configured for the service provider.
Inputs: no named parameters.
gorelo_list_time_entriesBRead-only
Lists logged time across every ticket and task, narrowed by any of the filters.
Inputs: cursor, taskIds, userIds, pageSize, +10 more.
gorelo_list_uptime_checksARead-only
Lists uptime checks for the service provider using cursor pagination. Results are sorted by createdOn descending (newest first).
Inputs: query, cursor, tagIds, typeIds, +2 more.
gorelo_list_usersARead-only
Lists users (technicians) for the service provider using cursor pagination. Results are sorted by user id ascending (oldest first).
Inputs: cursor, pageSize, statusIds.
gorelo_list_work_typesARead-only
Lists the work types configured for the service provider. Use a work type's Id as WorkTypeId when logging time against a ticket.
Inputs: no named parameters.
gorelo_restore_document_versionB
Makes an earlier version the current one.
Inputs: versionId (required), documentId (required).
gorelo_update_clientA
Updates an existing client. Only supplied (non-null) fields are changed.
Inputs: body (required), clientId (required).
gorelo_update_contactB
Updates a contact. Send only the fields you want to change.
Inputs: body (required), contactId (required).
gorelo_update_custom_assetA
Updates a custom asset. Send only the fields you want to change.
Inputs: body (required), customAssetId (required).
gorelo_update_documentB
Updates a document's title, body or placement. Send only the fields you want to change.
Inputs: body (required), documentId (required).
gorelo_update_projectA
Updates a project. Send only the fields you want to change.
Inputs: body (required), projectId (required).
gorelo_update_project_sectionA
Updates a section's title or colour. Send only the fields you want to change.
Inputs: body (required), projectId (required), sectionId (required).
gorelo_update_project_taskA
Updates a task. Send only the fields you want to change.
Inputs: body (required), taskId (required), projectId (required).
gorelo_update_ticketA
Partially updates a ticket. Send only the fields you want to change.
Inputs: body (required), ticketId (required).
gorelo_update_time_entryA
Partially updates a time entry. Send only the fields you want to change.
Inputs: body (required), timeEntryId (required).
gorelo_update_uptime_checkA
Updates an uptime check. Send only the fields you want to change.
Inputs: body (required), checkId (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 90 tools
Most tools are scoped by resource and action (ticket/project/document/asset) with descriptions that help distinguish them. Some boundaries blur between comments, conversations, and approvals on tickets/tasks, and between agent assets and custom assets.
All tools use a consistent gorelo_ prefix and snake_case verb_noun pattern such as list_, get_, create_, update_, duplicate_, and restore_. Compound names still follow the same predictable convention.
Ninety tools is far beyond a well-scoped MCP surface, even for a broad PSA/RMM platform. The volume creates high selection burden and suggests many operations should be grouped, trimmed, or exposed through more focused endpoints.
The surface covers many entities with list/get/create/update operations, but there are notable gaps: almost no delete operations, agent assets are read-only, invoices/contracts/items are mostly read-only, and forms lack get/create operations. These gaps will force agents to work around missing lifecycle operations.
Maintenance
Related MCP Connectors
One governed MCP endpoint for 40+ business systems. Read-only, source-cited answers.
The HubSpot MCP Server acts as a bridge that enables AI assistants and Large Language Models to securely interact with HubSpot CRM data through natural conversation, without requiring users to understand complex API structures. It provides read-only access to standard CRM objects (contacts, companies, deals, tickets, products, invoices, and more) and their associations, secured via OAuth 2.0, allowing AI agents to perform tasks like summarizing deals, fetching company updates, and looking up record changes.
Build and run AI workflows, agents, data tables and 1000+ API integrations from any MCP client.
Read-only MCP access to a documented IT fleet: state, changes, posture. 15 tools.
Related MCP Servers
- AlicenseCqualityCmaintenanceProvides AI assistants with direct access to Autotask PSA for MSP operations. Enables natural language interaction for ticket management, time logging, company lookups, project tracking, and billing review through 39 comprehensive tools.100Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to analyze IT support tickets, categorize urgency, suggest responses, and retrieve statistics via MCP tools.-
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to query internal business data for insights into customers, revenue, subscriptions, sales, and churn through controlled, read-only MCP tools.-
- AlicenseAqualityBmaintenanceProvides read-only visibility into CyberQP privileged access management data, including customer and account metadata, tenant event logs, and Just-In-Time account status and policies, for AI assistants.10Apache 2.0