Read tickets, devices, alerts and invoices; create tickets, add comments, log time in Gorelo. For managed service providers that run their helpdesk and device management in Gorelo. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"gorelo": {
"url": "https://gorelo.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"gorelo": {
"type": "http",
"url": "https://gorelo.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
List tickets with status, priority, client and assignees. Read the status list to filter for open tickets. Open one ticket to read its comments.
gorelo_list_tickets gorelo_list_ticket_statuses gorelo_list_ticket_comments
List managed devices for a client and check their status. Read the hardware and the pending Windows updates of one device.
gorelo_list_agent_assets gorelo_get_agent_hardware gorelo_list_agent_pending_updates
List invoices with status, totals and client. Open one invoice to read its line items. Read the contracts to compare the billing lines.
gorelo_list_invoices gorelo_get_invoice gorelo_list_contracts
Create a service ticket with a status, a technician group and a type. Look up the ids first with the list tools.
Changes data · gorelo_create_ticket gorelo_list_groups gorelo_list_ticket_types gorelo_list_ticket_statuses
Add a private note or a public reply to a ticket. Then log the hours that you worked on it.
Changes data · gorelo_add_ticket_comment gorelo_log_time_entry
Read the latest alerts. Link an alert to an open ticket or dismiss it.
Changes data · gorelo_list_alerts gorelo_update_alert_status
The login page asks for your Gorelo API key and Data region.
In Gorelo open Settings → Integrations → Generate New Key. A key can be scoped, so give it only the access you want. Your key is used only to call the Gorelo API for you and to derive a private account id.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Gorelo API key and Data region. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Gorelo connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
gorelo_list_clients | read | List clients List the MSP's clients (customers). Good first call to find a client id. API: GET /v1/clients. |
gorelo_get_client | read | Get a client Get one client by id with its details. API: GET /v1/clients/{clientId}. |
gorelo_list_client_locations | read | List client locations List the locations (sites) of one client. API: GET /v1/clients/{clientId}/locations. |
gorelo_list_contacts | read | List contacts List client contacts (end users). API: GET /v1/contacts. |
gorelo_get_contact | read | Get a contact Get one contact by id. API: GET /v1/contacts/{contactId}. |
gorelo_list_tickets | read | List tickets List service tickets, newest activity first, with status, priority, client, assignees and SLA. Use the list_ticket_statuses/types/priorities tools to learn the ids for filters. API: GET /v1/tickets. |
gorelo_get_ticket | read | Get a ticket Get one ticket by id (uuid). API: GET /v1/tickets/{ticketId}. |
gorelo_list_ticket_comments | read | List ticket comments List the comments (public replies, private notes) on a ticket. API: GET /v1/tickets/{ticketId}/comments. |
gorelo_list_ticket_statuses | read | List ticket statuses List the ticket statuses (id and name) used to filter or update tickets. API: GET /v1/tickets/statuses. |
gorelo_list_ticket_types | read | List ticket types List the ticket types. API: GET /v1/tickets/types. |
gorelo_list_ticket_priorities | read | List ticket priorities List the ticket priorities. API: GET /v1/tickets/priorities. |
gorelo_list_agent_assets | read | List managed devices List agent (RMM managed device) assets with status, OS and client. API: GET /v1/assets/agents. |
gorelo_get_agent_asset | read | Get a managed device Get one managed device by id (guid). API: GET /v1/assets/agents/{agentAssetId}. |
gorelo_get_agent_hardware | read | Get device hardware Get a managed device's processors, memory and disks. API: GET /v1/assets/agents/{agentAssetId}/hardware. |
gorelo_list_agent_pending_updates | read | List device pending updates List the Windows updates pending on a managed device, from its last scan (no new scan starts). API: GET /v1/assets/agents/{agentAssetId}/patches/available. |
gorelo_list_custom_assets | read | List custom assets List custom (non-agent) assets such as printers, switches and licences. API: GET /v1/assets/custom. |
gorelo_list_alerts | read | List alerts List alerts (uptime, script, external, ...) newest first. API: GET /v1/alerts. |
gorelo_get_alert | read | Get an alert Get one alert by id (guid). API: GET /v1/alerts/{alertId}. |
gorelo_list_projects | read | List projects List projects with status, client and lead. API: GET /v1/projects. |
gorelo_list_project_tasks | read | List project tasks List the tasks of one project. API: GET /v1/projects/{projectId}/tasks. |
gorelo_list_time_entries | read | List time entries List logged time across tickets and tasks. API: GET /v1/time-entries. |
gorelo_list_invoices | read | List invoices List invoices with status, totals and client. API: GET /v1/invoices. |
gorelo_get_invoice | read | Get an invoice Get one invoice with its line items and attachments. API: GET /v1/invoices/{invoiceId}. |
gorelo_list_contracts | read | List contracts List billing contracts with their service lines. API: GET /v1/contracts. |
gorelo_list_users | read | List technicians List users (technicians) with role and status; use their ids as assignee ids. API: GET /v1/organization/users. |
gorelo_list_groups | read | List technician groups List technician groups (ids are needed to create a ticket). API: GET /v1/organization/groups. |
gorelo_create_ticket | write | Create a ticket WRITE: create a service ticket. Needs status_id, group_id and type_id (use gorelo_list_ticket_statuses, gorelo_list_groups, gorelo_list_ticket_types). Set send_created_email true only if the contact must get a 'ticket created' email. API: POST /v1/tickets. |
gorelo_update_ticket | write | Update a ticket WRITE: change fields of a ticket (status, priority, assignee, title, tags). Only the fields you send change. Each change notifies and logs as in the app. Changing the client clears the ticket's contact and assets. API: PATCH /v1/tickets/{ticketId}. |
gorelo_add_ticket_comment | write | Add a ticket comment WRITE: add a comment to a ticket's main thread. A 'public' comment is a reply the client sees and may be emailed to them; a 'private' comment is an internal note. Do not retry after an unclear error: that can post twice. API: POST /v1/tickets/{ticketId}/comments. |
gorelo_update_alert_status | write | Update an alert status WRITE: dismiss an alert, restore it to New, or link it to an open ticket (status 'ticketed' needs ticket_id). The change applies to the alert's whole stack, as in the app. API: PATCH /v1/alerts/{alertId}. |
gorelo_log_time_entry | write | Log time on a ticket WRITE: log work time against a ticket (or a project task). Give any two of started_on, ended_on and actual_hours (the API derives the third). Billing role, work type and billable status default from the ticket. Do not retry after an unclear error: that can log twice. API: POST /v1/time-entries. |
gorelo_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
gorelo_request_feature | Request a missing feature Tell usefulapi that the user needs something the Gorelo tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
gorelo_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Gorelo (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
gorelo_cancel_subscription | Cancel the Pro subscription Cancel the caller's Gorelo Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run gorelo_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this Gorelo server only. Subscribe with gorelo_upgrade (it returns a Stripe Checkout link). Cancel any time with gorelo_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running gorelo_upgrade before then undoes the cancel. Or write to [email protected].
Review the open and unassigned tickets. Find the managed devices that need attention. Check overdue invoices per client. Open a ticket for a client problem. Add a note to a ticket and log the time. Handle an alert. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Gorelo. The server calls the Gorelo API with your own Gorelo access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Gorelo API key and Data region. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Gorelo API key and Data region. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Gorelo API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Gorelo.
Yes, if you approve it. 5 of the 31 Gorelo tools can create or change data. The other 26 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this Gorelo server only. Cancel any time: Pro then runs to the end of the paid period. Run gorelo_usage_status to see how many calls you used.
Ask the AI to run gorelo_upgrade: it returns a Stripe Checkout link. To cancel, run gorelo_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with gorelo_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.