Bind ERP MCP by usefulapi

할 수 있는 일

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

• 연결 방식: 클라우드에서 실행
• 전송 방식: Streamable HTTP
• 카테고리: 온라인 쇼핑몰 및 결제

설치

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

필요한 것

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

어떤 앱을 쓰세요?

https://bind-erp.usefulapi.io/mcp

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

{
  "mcpServers": {
    "bind-erp": {
      "url": "https://bind-erp.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "bind-erp": {
      "type": "http",
      "url": "https://bind-erp.usefulapi.io/mcp"
    }
  }
}

https://bind-erp.usefulapi.io/mcp

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

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

할 수 있는 일

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

• binderp_get_account

  The Bind ERP user and company this API key belongs to: user name, email, roles, branches (locations), company name, RFC (tax id), legal/commercial name, fiscal type and address. GET /api/UserProfile and /api/CompanyProfile.

• binderp_list_catalog

  List one of the reference catalogs whose ids other tools need: locations (branches), warehouses, price_lists, currencies, bank_accounts (with balances), users (employees) or categories. GET /api/Locations, /api/Warehouses, /api/PriceLists, /api/Currencies, /api/BankAccounts, /api

• binderp_list_clients

  List customers: id, number, name, legal name, RFC, email, phone, next contact date and branch. Filter with OData, e.g. substringof('acme', ClientName). GET /api/Clients.

• binderp_get_client

  One customer with credit terms (days and limit), payment method, price list, branch, sales and credit contacts, discount, account number and addresses. GET /api/Clients/{id}.

• binderp_get_client_addresses

  The addresses of a customer, with the ids that an order needs as address_id. GET /api/Clients/{id}/Addresses.

• binderp_list_prospects

  List sales prospects (leads): id, name, company, email, phone and salesperson. GET /api/Prospects.

• binderp_get_prospect

  One prospect: name, company, email, phone, comments, creation date and owner. GET /api/Prospects/{id}.

• binderp_list_providers

  List suppliers: id, number, name, legal name, RFC, email, phone and city. GET /api/Providers.

• binderp_list_products

  List products: id, code, title, SKU, cost, current inventory, VAT flag, unit, currency and categories. Filter with OData, e.g. substringof('tornillo', Title). GET /api/Products.

• binderp_get_product

  One product with prices per price list, inventory per warehouse, categories and alternative units. GET /api/Products/{id}.

• binderp_list_products_with_price_and_stock

  Products with the price (from one price list) and stock (in one warehouse), VAT/IEPS, min/max and volume prices: the view a point-of-sale or quote needs. Get the ids from binderp_list_catalog. GET /api/ProductsPriceAndInventory.

• binderp_get_inventory

  Stock of every product in one warehouse: current inventory, balance, quantity on client orders and on purchase orders, value and SKU. Filter with OData, e.g. CurrentInventory lt 5 for low stock. GET /api/Inventory?warehouseID=.

• binderp_list_invoices

  List sales invoices, with series, number, date, client, RFC, subtotal, discount, taxes, total, payments received, credit notes, expiration date and status. Open balance = Total - Payments - CreditNotes (filter Total gt Payments, then subtract CreditNotes from the rows). GET /api/

• binderp_get_invoice

  One sale with client, status, payment terms, branch, warehouse, currency, totals, payments, credit notes and its product and service lines. Takes the invoice GUID or its number. GET /api/Invoices/{idOrNumber}.

• binderp_list_invoice_payments

  The payments registered against one invoice: date, account, amount, status and who registered them. GET /api/Invoices/Payment/{invoiceID}.

• binderp_list_orders

  List customer orders (pedidos): number, date, client, branch, warehouse, salesperson, currency, subtotals, taxes, total and status. GET /api/Orders.

• binderp_get_order

  One customer order with address, status, totals and its product and service lines. GET /api/Orders/{id}.

• binderp_list_quotes

  List quotes (cotizaciones): number, date, client, branch, comments, total, currency and status. GET /api/Quotes.

• binderp_get_quote

  One quote with client or prospect, totals and its line items. GET /api/Quotes/{id}.

• binderp_list_purchase_orders

  List purchase orders to suppliers: number, warehouse, provider, date, status, quantity ordered and still missing, total and currency. GET /api/Purchases/GetPurchaseOrders.

• binderp_get_purchase_order

  One purchase order with its product lines, quantities received and totals. GET /api/Purchases/{id}.

• binderp_list_activities

  List CRM activities (calls, meetings, tasks): title, start and end, owner, done flag, type and the client or prospect they belong to. GET /api/Activities.

• binderp_create_prospect

  Create a sales prospect (lead) in Bind ERP. Writes a new record visible to the whole team; it is not deduplicated, so check binderp_list_prospects first. No message is sent to the prospect. POST /api/Prospects.

• binderp_create_client

  Create a customer in Bind ERP. Writes a new customer record (with credit terms) and is not deduplicated: check binderp_list_clients for the RFC first. The RFC must be valid for the tax authority (use XAXX010101000 for a generic public customer). No message is sent. Get price_list

• binderp_add_comment

  Add a comment to a Bind ERP record (client, prospect, order, ...) identified by its GUID. The comment becomes part of that record's history and cannot be removed through this API. POST /api/Comments.

• binderp_create_order

  Create a customer order (pedido, not an invoice: nothing is stamped or invoiced and no email is sent) with product and/or service lines. It reserves stock and shows up in the sales pipeline, so confirm client, prices and quantities first. Get ids from binderp_list_clients, binder

기본 점검i

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

• ✓ 통과

  제작자와 저장소 일치

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

• … 아직 점검 안 함

  계속 관리되고 있음

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

• … 아직 점검 안 함

  라이선스 있음

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

• ✓ 통과

  엔드포인트 응답

  88ms 만에 응답(HTTP 200)

• – 해당 없음

  OAuth로 로그인

  로그인 필요 없음

• ✓ 통과

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

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

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

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

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

대안

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

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

제작자의 README

{