UpKeep MCP by usefulapi

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 网店与支付

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

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

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月6日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

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

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

• ✓ 通过

  作者与仓库一致

  注册名称已通过域名 usefulapi.io 验证（注册中心会核实域名所有权）

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 70 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 29 个工具描述，未发现针对 AI 的隐藏指令

与“网店与支付”中的其他服务器比较i

• 星标数多于此分类中其他 1741 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 1741 个服务器的 94% 更新
• 基础检查结果等于或优于此分类中其他 1741 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

{