UpKeep MCP by usefulapi

io.usefulapi由 usefulapi.io 發布官方發布者v1.17.4更新於 Nov 7, 2026

Read UpKeep work orders, assets, parts and meters; create requests and work orders.

發布方自己的服務:Ably MCP by usefulapi

已驗證Streamable HTTP可網頁執行效率與工作流資料與分析商業與電商

概覽

AI 產生的概覽

將助理接入 UpKeep 維護管理系統,可讀取工單、資產、備件和儀表,並建立請求與工單。

可以做什麼
  • 瀏覽與檢視工單、工作請求及預防性維護計畫,含檢查項目、工時紀錄和備件
  • 查詢資產、位置、儀表及儀表讀數,並登錄新讀數
  • 查看備件庫存、成本和補貨門檻,並設定備件數量
  • 查看使用者、團隊、供應商、客戶和採購單
  • 建立與核准工作請求,建立或更新工單,並在工單上留言
  • 檢查 API 權杖狀態和每月工具呼叫用量
適用情境
適合在 UpKeep 中管理維護作業時使用:讓助理回答逾期或高優先工單、資產與庫存狀況等問題,或直接提交與核准請求及工單,不必切換應用程式。
執行需求
以 URL 方式加入的遠端 MCP 端點;伺服器透過 OAuth 登入,登入頁面要求填寫 UpKeep 憑證。首次連線時需貼上 UpKeep 組織 API 權杖(位於設定中的 API Tokens)。用戶端設定中不要加入 API 金鑰或 Authorization 標頭。超出免費每月呼叫額度後需付費方案。
安裝前請注意
寫入類工具會變更 UpKeep 資料:建立與核准請求、建立和更新工單、張貼留言、新增儀表讀數以及覆寫備件數量。核准請求會將其轉為工單,完成工單可能觸發帳戶整合;通知可能送達負責人與核准人。UpKeep 組織 API 權杖屬於憑證。用量按次計量,付費方案透過付款連結結帳。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 UpKeep MCP by usefulapi,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.usefulapi%2Fupkeep/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "upkeep-by-usefulapi": {
      "type": "http",
      "url": "https://upkeep.usefulapi.io/mcp"
    }
  }
}

README

UpKeep MCP by usefulapi

Read UpKeep work orders, assets, parts and meters; create requests and work orders.

Live endpoint: https://upkeep.usefulapi.io/mcp · Homepage: https://usefulapi.io/upkeep

Connect

  • Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste https://upkeep.usefulapi.io/mcp.
  • Claude Code: claude mcp add --transport http upkeep https://upkeep.usefulapi.io/mcp, then run /mcp to log in.
  • VS Code: Add to VS Code.
  • Cursor and other clients: add the URL as a remote MCP server:
json
{  "mcpServers": {    "upkeep": {      "url": "https://upkeep.usefulapi.io/mcp"    }  }}

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, and the login page asks for your UpKeep credentials.

Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/upkeep/

On first connect you'll paste an UpKeep organization API token (Settings → API Tokens; it starts with uk_pat_).

Tools

ToolTypeWhat it does
upkeep_get_accountreadCheck API token
upkeep_list_work_ordersreadList work orders
upkeep_get_work_orderreadGet work order
upkeep_list_assetsreadList assets
upkeep_get_assetreadGet asset
upkeep_list_locationsreadList locations
upkeep_get_locationreadGet location
upkeep_list_partsreadList parts (inventory)
upkeep_get_partreadGet part
upkeep_list_metersreadList meters
upkeep_get_meterreadGet meter
upkeep_list_meter_readingsreadList meter readings
upkeep_add_meter_readingwriteAdd meter reading
upkeep_list_requestsreadList work requests
upkeep_get_requestreadGet work request
upkeep_create_requestwriteCreate work request
upkeep_approve_requestwriteApprove work request
upkeep_create_work_orderwriteCreate work order
upkeep_update_work_orderwriteUpdate work order
upkeep_add_work_order_messagewriteAdd work order message
upkeep_update_part_quantitywriteUpdate part quantity
upkeep_list_usersreadList users
upkeep_get_userreadGet user
upkeep_list_teamsreadList teams
upkeep_list_vendorsreadList vendors
upkeep_list_customersreadList customers
upkeep_list_purchase_ordersreadList purchase orders
upkeep_get_purchase_orderreadGet purchase order
upkeep_list_preventive_maintenancereadList preventive maintenance plans
upkeep_usage_statusmetaUsage status (free-tier meter)
upkeep_request_featuremetaRequest a missing feature
upkeep_upgrademetaUpgrade to Pro or Pro+
upkeep_cancel_subscriptionmetaCancel the Pro subscription

read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.

Pricing

PlanPriceLimit
Free$050 tool calls / month
Pro (per user)$9/mo or $90/yr (2 months free)Unlimited*

*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to [email protected].

Pro covers this server only. Subscribe with upkeep_upgrade (it returns a Stripe Checkout link). Cancel any time with upkeep_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running upkeep_upgrade before then undoes the cancel. Or write to [email protected].

License

MIT © usefulapi. Not affiliated with or endorsed by UpKeep.

來源:servers/upkeep/README.md,提交 4046075

工具

29

upkeep_get_account

Check API token

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

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.

輸入參數assetlimittitleoffsetstatusarchivedcategoryincludeslocationorder_byprioritydue_after另有 11 個

upkeep_get_work_order

Get work order

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

輸入參數includeswork_order_id必填

upkeep_list_assets

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.

輸入參數namelimitoffsetstatusbarcodecategoryincludeslocationorder_bycreated_afterserial_numberupdated_after另有 4 個

upkeep_get_asset

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

輸入參數asset_id必填includes

upkeep_list_locations

List locations

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

輸入參數namelimitoffsetbarcodeincludesorder_bycreated_afterupdated_aftercreated_beforeupdated_beforehierarchy_levelparent_location

upkeep_get_location

Get location

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

輸入參數location_id必填

upkeep_list_parts

List parts (inventory)

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.

輸入參數namelimitoffsetcategoryincludeslocationorder_bypart_numbercreated_afterupdated_aftercreated_beforeupdated_before

upkeep_get_part

Get part

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

輸入參數part_id必填

upkeep_list_meters

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.

輸入參數nameassetlimitoffsetincludeslocationorder_bycreated_afterupdated_aftercreated_beforeupdated_before

upkeep_get_meter

Get meter

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

輸入參數meter_id必填

upkeep_list_meter_readings

List meter readings

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

輸入參數limitoffsetmeter_id必填order_byread_afterread_before

upkeep_add_meter_reading

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.

輸入參數datevalue必填meter_id必填

upkeep_list_requests

List work requests

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

輸入參數teamassetlimitoffsetcategoryincludeslocationorder_bycreated_afterupdated_aftercreated_beforerequest_status另有 4 個

upkeep_get_request

Get work request

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

輸入參數request_id必填

upkeep_create_request

Create work 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 /requests.

輸入參數teamassettitle必填fieldscategorydue_datelocationprioritydescriptionassigned_to_user

upkeep_approve_request

Approve work 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.

輸入參數request_id必填

upkeep_create_work_order

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.

輸入參數assettitle必填categorydue_datelocationprioritystart_datedescriptionassigned_to_userestimated_duration_hours

upkeep_update_work_order

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 deleting are not offered. PATCH /work-orders/{id}.

輸入參數titlestatusdue_dateprioritydescriptionwork_order_id必填assigned_to_user

upkeep_add_work_order_message

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.

輸入參數text必填work_order_id必填

upkeep_update_part_quantity

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

輸入參數part_id必填quantity必填minimum_quantity

upkeep_list_users

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.

輸入參數emaillimitoffsetorder_byaccount_typecreated_afterupdated_aftercreated_beforeupdated_before

upkeep_get_user

Get user

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

輸入參數user_id必填

upkeep_list_teams

List teams

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

輸入參數namelimitoffset

upkeep_list_vendors

List vendors

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

輸入參數limitoffsetbusiness_name

upkeep_list_customers

List customers

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

輸入參數namelimitoffset

upkeep_list_purchase_orders

List purchase orders

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

輸入參數limittitleoffsetstatusvendorcategoryincludesorder_bydue_afterdue_beforecreated_afterupdated_after另有 2 個

upkeep_get_purchase_order

Get purchase order

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

輸入參數purchase_order_id必填

upkeep_list_preventive_maintenance

List preventive maintenance plans

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.

輸入參數pageteamassetsearchassigneelocationprioritypage_sizeinclude_schedules

版本歷史

15
  1. v1.17.4最新Nov 7, 2026
  2. v1.16.3Nov 5, 2026
  3. v1.16.2Nov 5, 2026
  4. v1.16.1Nov 4, 2026
  5. v1.16.0Nov 3, 2026
  6. v1.15.1Nov 3, 2026
  7. v1.14.0Nov 1, 2026
  8. v1.12.0Oct 31, 2026
  9. v1.11.0Oct 31, 2026
  10. v1.10.2Oct 30, 2026
  11. v1.10.0Oct 30, 2026
  12. v1.5.0Oct 26, 2026
  13. v1.2.3Oct 25, 2026
  14. v1.2.0Oct 25, 2026
  15. v1.1.0Oct 24, 2026

評分

已滿足適用檢查項的 100%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

其他 Usefulapi 整合