PHP Point of Sale MCP by usefulapi

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

• 연결 방식: 클라우드에서 실행
• 전송 방식: Streamable HTTP
• 카테고리: 회계, 재무 및 세금

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

필요한 것

• 클라우드에서 실행설치할 것 없음. 인터넷으로 연결돼요

어떤 앱을 쓰세요?

https://php-point-of-sale.usefulapi.io/mcp

claude mcp add --transport http php-point-of-sale https://php-point-of-sale.usefulapi.io/mcp

{
  "mcpServers": {
    "php-point-of-sale": {
      "url": "https://php-point-of-sale.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "php-point-of-sale": {
      "type": "http",
      "url": "https://php-point-of-sale.usefulapi.io/mcp"
    }
  }
}

https://php-point-of-sale.usefulapi.io/mcp

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

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

도구 이름과 설명은 서버가 2026년 11월 8일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.

• phppos_list_locations

  List the store's locations (shops/warehouses) with name, address, phone, email, time zone and default tax rates, plus each location's registers (id and name). Use the location ids to filter sales, expenses, customers and reports. Payment-processor credentials and device settings

• phppos_list_items

  List or search inventory items with name, item number, category, supplier, prices and reorder level. Search by text, or by one field (name, item_number, product_id, supplier, tag_name...). GET /items.

• phppos_get_item

  One inventory item by id: prices, tax settings, category, supplier, tags, attributes, variations, tier pricing and per-location settings. GET /items/{id}.

• phppos_list_categories

  List item categories with their ids. Use the ids to filter items or to file a new item. GET /categories.

• phppos_list_item_kits

  List item kits (bundles of items sold together) with their prices. GET /item_kits.

• phppos_list_sales

  List or search completed sales, by date range, customer (id or email) or location. verbosity: minimal (headline fields), medium (adds customer, totals, profit, location - the default here) or full (every line item, payment and tax). Suspended sales (layaways, estimates) are fetch

• phppos_get_sale

  One sale by id with line items, payments, taxes, customer and employee (verbosity full by default). GET /sales/{id}.

• phppos_list_receivings

  List receivings (stock received from suppliers, purchase orders, transfers) with supplier, totals and items, by date range. GET /receivings.

• phppos_get_receiving

  One receiving by id: supplier, items, quantities, costs and payments. GET /receivings/{id}.

• phppos_list_customers

  List or search customers with contact details, tier, store-account balance, credit limit and loyalty points. Search by text or by one field (email, phone_number, first_name, last_name, account_number). GET /customers.

• phppos_get_customer

  One customer by person id: contact details, tier, tax settings, balance, credit limit, points, notes and custom fields. GET /customers/{person_id}.

• phppos_list_suppliers

  List or search suppliers with contact details, company, account number and balance. GET /suppliers.

• phppos_get_supplier

  One supplier by person id. GET /suppliers/{person_id}.

• phppos_list_employees

  List employees with name, contact details, username, hire date, manager, commission and pay rate settings and assigned locations. Passwords and the permission maps are never returned. GET /employees.

• phppos_list_invoices

  List customer invoices (money customers owe) or supplier invoices (money the store owes) with date, due date, status and amount. GET /invoices/customer or /invoices/supplier.

• phppos_list_expenses

  List recorded expenses with type, description, date, amount, tax, payment type, category and location. GET /expenses.

• phppos_list_gift_cards

  List gift cards with number, description, remaining value, customer and whether inactive. GET /giftcards.

• phppos_get_gift_card

  One gift card by its card number (or id): remaining value, customer and status. GET /giftcards/{giftcard_number}.

• phppos_list_appointments

  List appointments (bookings) with customer, employee, service, start and end time, optionally within a time window. GET /appointments.

• phppos_list_reports

  The catalog of the store's reports (138 of them: sales summaries, top sellers, inventory low/aging/summary, profit and loss, taxes, payments, employee, customer, supplier and store-account reports) with the inputs each accepts. Without `search` only the report keys are returned;

• phppos_run_report

  Run one of the store's reports and return it (title, summary, detail rows); `paging.next_offset` is set when more detail rows remain. Report keys and their inputs come from phppos_list_reports (for example summary_sales, top_sellers, inventory_low, summary_profit_and_loss, summar

• phppos_create_customer

  WRITE: create a customer in the store. Store-account balance, credit limit and loyalty points cannot be set here. Needs a Read/Write API key. Retrying creates a duplicate (check phppos_list_customers first). The store's 'new customer' webhook, if configured, fires. POST /customer

• phppos_update_customer

  WRITE: change fields of an existing customer; only the fields you pass are sent. Overwrites the current values. Needs a Read/Write API key. The store's 'edit customer' webhook, if configured, fires. POST /customers/{person_id}.

• phppos_create_item

  WRITE: create an inventory item (name required). Stock quantities are not set here. Needs a Read/Write API key. Retrying creates a duplicate (search with phppos_list_items first). The store's item webhooks, if configured, fire. POST /items.

• phppos_update_item

  WRITE: change fields of an existing item (for example its price, category or active state); only the fields you pass are sent. Overwrites the current values, and a price change applies to the next sale. Needs a Read/Write API key. The store's 'edit item' webhook, if configured, f

• phppos_create_expense

  WRITE: record an expense in the store's books (description, amount and date). It affects expense and profit-and-loss reports. Needs a Read/Write API key. Retrying records it twice (check phppos_list_expenses first). POST /expenses.

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 8일 점검

• ✓ 통과

  제작자와 저장소 일치

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

• … 아직 점검 안 함

  계속 관리되고 있음

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

• … 아직 점검 안 함

  라이선스 있음

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

• ✓ 통과

  엔드포인트 응답

  26ms 만에 응답(HTTP 200)

• – 해당 없음

  OAuth로 로그인

  로그인 필요 없음

• ✓ 통과

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

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

회계, 재무 및 세금 카테고리의 다른 서버와 비교i

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

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

대안

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

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

제작자의 README

{