
Gorelo
io.github.WYRE-AI由 GitHub 账号 WYRE-AI 发布v1.1.1更新于 Oct 29, 2026
MCP server for Gorelo's PSA ticket, client, contact, contract, asset, and time-tracking APIs.
概览
本地 MCP 服务器,封装 Gorelo 的 PSA REST API,让助手读写工单、客户、联系人、资产、项目、文档与账单数据。
- 可以做什么
- 查询、创建和更新工单、评论、审批与侧边会话
- 管理客户、联系人、地点、技术员分组与用户
- 处理资产、自定义资产、可用性检查与告警
- 浏览和编辑项目、分区、任务、评论与审批
- 读取与创建文档、表单及表单提交链接
- 读取合同、发票、目录项与工时记录,可选创建发票、付款与目录项
- 适用场景
- 适合以 Gorelo 作为服务台系统的托管服务商或 IT 团队,让助手在不切换工具的情况下查询工单与客户、起草更新、登记工时,或汇总项目与账单信息。
- 运行要求
- 以本地进程(stdio)方式运行已发布的容器镜像,或以 HTTP 方式用于网关托管。需要 Gorelo 公共 API 密钥(GORELO_API_KEY,作为 X-API-Key 请求头发送)以及正确的 GORELO_REGION(us 或 au)。HTTP 模式还需 CONDUIT_S2S_SECRET。需要能访问 Gorelo API 的网络。
安装
在 SourceWeft 中
- 打开 控制台中的 Gorelo,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
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:
来源:README.md,提交 bf4e924
工具
0版本历史
4- v1.1.1最新Oct 22, 2026
- v1.1.0Oct 20, 2026
- v1.0.1Oct 14, 2026
- v1.0.0Sep 20, 2026
评分
已满足适用检查项的 40%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分
请在仓库或注册中心条目中声明许可证。