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

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

이 설정은 제작자의 레지스트리 정보로 만들었어요. 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월 7일 점검

• ✓ 통과

  제작자와 저장소 일치

  레지스트리 이름이 도메인 usefulapi.io 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)

• … 아직 점검 안 함

  계속 관리되고 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• … 아직 점검 안 함

  라이선스 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• ✓ 통과

  엔드포인트 응답

  70ms 만에 응답(HTTP 200)

• – 해당 없음

  OAuth로 로그인

  로그인 필요 없음

• ✓ 통과

  도구 설명에 숨겨진 지시 없음

  도구 설명 29개를 읽었고, AI에게 보내는 숨겨진 지시는 없었어요

온라인 쇼핑몰 및 결제 카테고리의 다른 서버와 비교i

• 이 카테고리의 다른 서버 1751개 중 0%보다 스타가 많아요
• 이 카테고리의 다른 서버 1751개 중 95%보다 최근에 레지스트리에 공개됐어요
• 기본 점검 결과가 이 카테고리의 다른 서버 1751개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

제작자의 README

{