Gorelo MCP by usefulapi

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Other

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

https://gorelo.usefulapi.io/mcp

claude mcp add --transport http gorelo https://gorelo.usefulapi.io/mcp

{
  "mcpServers": {
    "gorelo": {
      "url": "https://gorelo.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "gorelo": {
      "type": "http",
      "url": "https://gorelo.usefulapi.io/mcp"
    }
  }
}

https://gorelo.usefulapi.io/mcp

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

• gorelo_list_clients

  List the MSP's clients (customers). Good first call to find a client id. API: GET /v1/clients.

• gorelo_get_client

  Get one client by id with its details. API: GET /v1/clients/{clientId}.

• gorelo_list_client_locations

  List the locations (sites) of one client. API: GET /v1/clients/{clientId}/locations.

• gorelo_list_contacts

  List client contacts (end users). API: GET /v1/contacts.

• gorelo_get_contact

  Get one contact by id. API: GET /v1/contacts/{contactId}.

• gorelo_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

  Get one ticket by id (uuid). API: GET /v1/tickets/{ticketId}.

• gorelo_list_ticket_comments

  List the comments (public replies, private notes) on a ticket. API: GET /v1/tickets/{ticketId}/comments.

• gorelo_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

  List the ticket types. API: GET /v1/tickets/types.

• gorelo_list_ticket_priorities

  List the ticket priorities. API: GET /v1/tickets/priorities.

• gorelo_list_agent_assets

  List agent (RMM managed device) assets with status, OS and client. API: GET /v1/assets/agents.

• gorelo_get_agent_asset

  Get one managed device by id (guid). API: GET /v1/assets/agents/{agentAssetId}.

• gorelo_get_agent_hardware

  Get a managed device's processors, memory and disks. API: GET /v1/assets/agents/{agentAssetId}/hardware.

• gorelo_list_agent_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

  List custom (non-agent) assets such as printers, switches and licences. API: GET /v1/assets/custom.

• gorelo_list_alerts

  List alerts (uptime, script, external, ...) newest first. API: GET /v1/alerts.

• gorelo_get_alert

  Get one alert by id (guid). API: GET /v1/alerts/{alertId}.

• gorelo_list_projects

  List projects with status, client and lead. API: GET /v1/projects.

• gorelo_list_project_tasks

  List the tasks of one project. API: GET /v1/projects/{projectId}/tasks.

• gorelo_list_time_entries

  List logged time across tickets and tasks. API: GET /v1/time-entries.

• gorelo_list_invoices

  List invoices with status, totals and client. API: GET /v1/invoices.

• gorelo_get_invoice

  Get one invoice with its line items and attachments. API: GET /v1/invoices/{invoiceId}.

• gorelo_list_contracts

  List billing contracts with their service lines. API: GET /v1/contracts.

• gorelo_list_users

  List users (technicians) with role and status; use their ids as assignee ids. API: GET /v1/organization/users.

• gorelo_list_groups

  List technician groups (ids are needed to create a ticket). API: GET /v1/organization/groups.

• gorelo_create_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: 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 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: 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 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 /v

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 11 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 31 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

• More stars than 0% of the other 32417 servers in this category
• Published to the registry more recently than 97% of the other 32417 servers in this category
• Basic checks equal to or better than 100% of the other 32417 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

{