
Gorelo
io.github.WYRE-AIPublished by GitHub account WYRE-AIv1.1.1Updated Oct 29, 2026
MCP server for Gorelo's PSA ticket, client, contact, contract, asset, and time-tracking APIs.
Overview
Local MCP server exposing Gorelo's PSA REST API, letting an assistant read and manage tickets, clients, contacts, assets, projects, documents and billing.
- What you can do
- List, read, create and update tickets, comments, approvals and side conversations
- Manage clients, contacts, locations, groups and users
- Work with assets, custom assets, uptime checks and alerts
- Browse and edit projects, sections, tasks, comments and approvals
- Read and create documents, forms and form submission links
- Read billing data (contracts, invoices, items, time entries) and optionally create invoices, payments and catalog items
- When to use it
- Useful for managed service providers or IT teams that run their service desk on Gorelo and want an assistant to look up tickets and clients, draft updates, log time, or summarise projects and billing without switching tools.
- Requirements
- Runs as a local process (stdio) from the published container image, or over HTTP for gateway hosting. Needs a Gorelo Public API key in GORELO_API_KEY (sent as the X-API-Key header) and the correct GORELO_REGION (us or au). HTTP mode additionally requires CONDUIT_S2S_SECRET. Network access to the Gorelo API is required.
Installation
In SourceWeft
- Open Gorelo in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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.
Configuration
Copy .env.example and set the variables below.
/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.
Request 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:
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
Assets
Billing
Clients
Contacts
Deletions
Documents
Forms
Organization
Projects
Tickets
tools/list size
Measured as the JSON size of the tools/list result (names, descriptions, input schemas, annotations):
Use a preset or GORELO_TOOLS_INCLUDE to shrink the list for clients with tight context budgets.
Tool selection
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:
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
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
Docker
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.
Compose 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.
Single-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses GORELO_API_KEY:
Local 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:
Source: README.md at commit bf4e924
Tools
0Version history
4- v1.1.1LatestOct 22, 2026
- v1.1.0Oct 20, 2026
- v1.0.1Oct 14, 2026
- v1.0.0Sep 20, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.