UpKeep 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: Online shops & payments

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://upkeep.usefulapi.io/mcp

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

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

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

https://upkeep.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.

• upkeep_get_account

  Confirm the UpKeep API token is active: returns the company id, the token's name, when it was created and when it was last used. GET /api/v1/organization-api-tokens/introspect.

• upkeep_list_work_orders

  List work orders (reactive and preventive), newest first, with status, priority, due date, asset, location, assignee, parts, time and cost. Filter by status, completion, priority, category, asset, location, assignee, title or date ranges. GET /work-orders.

• upkeep_get_work_order

  One work order by id with its checklist items, custom fields, time log, parts and files. GET /work-orders/{id}.

• upkeep_list_assets

  List assets (equipment) with name, model, serial and barcode, location, status, downtime status, warranty and number of open work orders. Filter by name, serial number, barcode, location, status, category or assignee. GET /assets.

• upkeep_get_asset

  One asset by id with purchase and warranty details, custom fields and (optionally) assigned users, teams, vendors, parts, files and sub-assets. GET /assets/{id}.

• upkeep_list_locations

  List locations (sites, buildings, rooms) with address, barcode, parent location and hierarchy level. GET /locations.

• upkeep_get_location

  One location by id. GET /locations/{id}.

• upkeep_list_parts

  List spare parts with quantity on hand, minimum quantity, cost, category, location and part number. Compare quantity with minimumQuantity to find parts to reorder. GET /parts.

• upkeep_get_part

  One part by id with quantity, cost, location and custom fields. GET /parts/{id}.

• upkeep_list_meters

  List meters (usage counters such as hours, mileage, temperature) with units, reading frequency and the asset or location they belong to. GET /meters.

• upkeep_get_meter

  One meter by id. GET /meters/{id}.

• upkeep_list_meter_readings

  Readings recorded for one meter (value, date, who recorded it), newest first. GET /meters/{id}/readings.

• upkeep_add_meter_reading

  WRITE: record a new reading on a meter (for example engine hours or mileage). A reading cannot be removed with this server, and a meter notification can create a work order automatically when its condition is met. POST /meters/{id}/readings.

• upkeep_list_requests

  List work requests submitted by staff or through the request portal (before they become work orders), with status open/approved/rejected. GET /requests.

• upkeep_get_request

  One work request by id with its form fields and, once approved, the linked work order id. GET /requests/{id}.

• upkeep_create_request

  WRITE: submit a new work request for the maintenance team to approve (it appears in UpKeep's Requests list and may notify the approvers or the assignee). It is not a work order until approved. If the account has a request form configured, pass its field labels in `fields`. POST /

• upkeep_approve_request

  WRITE: approve a pending work request, which converts it into a work order (it may notify the assignee). Needs a token whose role may approve requests. Approving a request that is already approved or declined fails with HTTP 409. POST /requests/{id}/approve.

• upkeep_create_work_order

  WRITE: create a new work order (it may notify the assignee and appears in UpKeep's work order board). Ids for asset, location and assignee come from the list tools. POST /work-orders.

• upkeep_update_work_order

  WRITE: change fields of an existing work order: status (open, onHold, inProgress, complete), title, description, priority, due date or assignee. Only the fields you pass change; completing a work order may trigger the account's integrations (for example Zapier). Archiving and del

• upkeep_add_work_order_message

  WRITE: post a message (comment) on a work order's activity thread; people following the work order may be notified. POST /work-orders/{id}/update-messages.

• upkeep_update_part_quantity

  WRITE: set the quantity on hand (and optionally the minimum quantity that triggers a low-stock notification) of a part. This overwrites the stored number: read the part first and pass the new total, not the difference. PATCH /parts/{id}.

• upkeep_list_users

  List UpKeep users (technicians, admins, requesters) with account type, job title, status and last login. Use the ids to assign work orders. GET /users.

• upkeep_get_user

  One user by id. GET /users/{id}.

• upkeep_list_teams

  List teams with name and description. Use the ids to assign work. GET /teams.

• upkeep_list_vendors

  List vendors (suppliers and contractors) with contact details. GET /vendors.

• upkeep_list_customers

  List customers (the parties whose assets or locations you maintain) with contact details. GET /customers.

• upkeep_list_purchase_orders

  List purchase orders with status (awaiting, approved, declined, fulfilled), vendor, dates, total cost and quantities. GET /purchase-orders.

• upkeep_get_purchase_order

  One purchase order by id with its parts, quantities, costs and shipping details. GET /purchase-orders/{id}.

• upkeep_list_preventive_maintenance

  List preventive maintenance (PM) templates, the recurring work that generates scheduled work orders, with their schedules. Filter by text, asset, location, assignee, team or priority. Pages are 1-based. GET /pm.

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 70 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

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

Compared with others in Online shops & paymentsi

• More stars than 0% of the other 1741 servers in this category
• Published to the registry more recently than 94% of the other 1741 servers in this category
• Basic checks equal to or better than 100% of the other 1741 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

{