DecoNetwork MCP by usefulapi
Read production orders, mark orders produced or shipped, and add internal notes.
¿Debería usar esto?
Calidad y seguridad
Hallazgos (1)
- LOWen deconetwork_update_order_status
Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.
Costo de contexto
Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.
Instalar
Instalación con un clic
Agrega esto a tu archivo `claude_desktop_config.json`:
{
"mcpServers": {
"deconetwork": {
"url": "https://deconetwork.usefulapi.io/mcp"
}
}
}Puntos de conexión remotos
https://deconetwork.usefulapi.io/mcpstreamable-httpQué puede hacer
Inventario de herramientas
Herramientas (5)
🟢deconetwork_search_orders(invoice_number, ordered_from, ordered_to, due_from, due_to, ...)
Search DecoNetwork orders by date ordered, date due, date shipped, date invoiced or date modified (each a from/to range) and/or invoice number. Conditions are ANDed; with no filter the last 30 days of orders (by date ordered) are returned. Returns a compact summary per order: invoice number (order_id), job name, order and payment status in words, dates, amounts, billing and ship-to contact, shipping method, tracking numbers and line items. Use deconetwork_get_order for everything on one order. order_status narrows the page after it is fetched (the vendor has no documented status filter), so it must be combined with a date range or invoice number; page with next_offset. Max 100 rows per call; total and next_offset page through the rest. GET /api/json/manage_orders/find.
Esquema de entrada
{
"type": "object",
"properties": {
"invoice_number": {
"description": "Only the order with exactly this invoice number.",
"type": "string",
"minLength": 1,
"maxLength": 100
},
"ordered_from": {
"description": "Orders placed on or after this UTC date (date ordered).",
"type": "string"
},
"ordered_to": {
"description": "Orders placed on or before this UTC date (a bare date means end of that day).",
"type": "string"
},
"due_from": {
"description": "Orders due on or after this UTC date.",
"type": "string"
},
"due_to": {
"description": "Orders due on or before this UTC date.",
"type": "string"
},
"shipped_from": {
"description": "Orders shipped on or after this UTC date.",
"type": "string"
},
"shipped_to": {
"description": "Orders shipped on or before this UTC date.",
"type": "string"
},
"invoiced_from": {
"description": "Orders invoiced on or after this UTC date.",
"type": "string"
},
"invoiced_to": {
"description": "Orders invoiced on or before this UTC date.",
"type": "string"
},
"modified_from": {
"description": "Orders changed on or after this UTC date.",
"type": "string"
},
"modified_to": {
"description": "Orders changed on or before this UTC date.",
"type": "string"
},
"order_status": {
"description": "Keep only orders in these statuses (applied to the fetched page): ready for production, ready for shipping, shipped, cancelled, deleted, on hold, awaiting purchase order, awaiting stock, awaiting artwork.",
"maxItems": 10,
"type": "array",
"items": {
"type": "string",
"enum": [
"ready for production",
"ready for shipping",
"shipped",
"cancelled",
"deleted",
"on hold",
"awaiting purchase order",
"awaiting stock",
"awaiting artwork"
]
}
},
"sort_by": {
"description": "Sort field (default: production files ready).",
"type": "string",
"enum": [
"date_ordered",
"production_files_ready",
"invoice_number",
"order_status",
"date_due",
"date_shipped",
"date_invoiced",
"date_modified"
]
},
"include_shipments": {
"description": "Also load shipments (tracking, packages). Tracking numbers are listed either way when loaded.",
"type": "boolean"
},
"limit": {
"description": "Rows per call, 1-100 (default 25).",
"type": "integer",
"minimum": 1,
"maximum": 100
},
"offset": {
"description": "Rows to skip (default 0). Pass the previous reply's next_offset.",
"type": "integer",
"minimum": 0,
"maximum": 1000000
}
},
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🟢deconetwork_get_order(order_id, include_workflow_data, include_po_data, include_production_file_info)
One order by invoice number with everything the API holds: all line items with decoration views/areas/processes, fields and sizes, team names, payments, refunds, shipments with tracking and packages, notes, taxes, store, and (optional) workflow items and purchase-order data. Status codes are spelled out. Card numbers, coupons and credential-bearing document/media links are removed. Supplier catalog tools are unavailable. GET /api/json/manage_orders/find (invoice number condition).
Esquema de entrada
{
"type": "object",
"properties": {
"order_id": {
"type": "string",
"minLength": 1,
"maxLength": 100,
"description": "The order's invoice number, e.g. INV1234 (this is the order id)."
},
"include_workflow_data": {
"description": "Include production workflow items (what is left to produce or ship).",
"type": "boolean"
},
"include_po_data": {
"description": "Include purchase orders linked to the workflow items (implies workflow data).",
"type": "boolean"
},
"include_production_file_info": {
"description": "Include production file format, size and offsets per decoration.",
"type": "boolean"
}
},
"required": [
"order_id"
],
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🟢deconetwork_list_orders_due(due_from, due_to, include_closed, limit, offset)
Orders due in a date window (default: the next 7 days from today, UTC), soonest first, as compact summaries. By default cancelled, deleted and already shipped orders are left out, so the list is the work still ahead; set include_closed to see them. Use to answer 'what has to ship this week?'. GET /api/json/manage_orders/find (date due condition).
Esquema de entrada
{
"type": "object",
"properties": {
"due_from": {
"description": "Window start (default: today).",
"type": "string"
},
"due_to": {
"description": "Window end (default: 7 days after today).",
"type": "string"
},
"include_closed": {
"description": "Also return shipped, cancelled and deleted orders.",
"type": "boolean"
},
"limit": {
"description": "Rows per call, 1-100 (default 25).",
"type": "integer",
"minimum": 1,
"maximum": 100
},
"offset": {
"description": "Rows to skip (default 0). Pass the previous reply's next_offset.",
"type": "integer",
"minimum": 0,
"maximum": 1000000
}
},
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🔴deconetwork_update_order_status(order_id, new_status, order_line_id, workflow_item_id, qty, ...)
WRITE: move a whole order, one line item or part of a line item to 'produced' or 'shipped'. Cannot be undone through the API. With new_status shipped you can store a tracking number (shipping_code). contact_customer=true makes DecoNetwork EMAIL THE CUSTOMER about the change (only when the whole order changes status); it defaults to false, so set it only when the user asked to notify the customer. Give order_line_id to change one line, plus workflow_item_id (and optionally qty) to change part of it. POST /api/json/manage_orders/update_order_status.
Esquema de entrada
{
"type": "object",
"properties": {
"order_id": {
"type": "string",
"minLength": 1,
"maxLength": 100,
"description": "The order's invoice number, e.g. INV1234 (this is the order id)."
},
"new_status": {
"type": "string",
"enum": [
"produced",
"shipped"
],
"description": "produced (status 2) or shipped (status 3)."
},
"order_line_id": {
"description": "Only this line item (omit for the whole order).",
"type": "integer",
"exclusiveMinimum": 0,
"maximum": 9007199254740991
},
"workflow_item_id": {
"description": "Only this workflow item of the line (see deconetwork_get_order with include_workflow_data).",
"type": "integer",
"exclusiveMinimum": 0,
"maximum": 9007199254740991
},
"qty": {
"description": "Quantity to move; needs workflow_item_id. Default: the outstanding quantity.",
"type": "integer",
"exclusiveMinimum": 0,
"maximum": 1000000
},
"shipping_code": {
"description": "Tracking number to store when marking shipped.",
"type": "string",
"minLength": 1,
"maxLength": 200
},
"contact_customer": {
"description": "Email the customer about this change (default false). Whole-order changes only.",
"type": "boolean"
},
"operator_login": {
"description": "Login of the operator to credit (default: the connected staff account).",
"type": "string",
"minLength": 1,
"maxLength": 100
}
},
"required": [
"order_id",
"new_status"
],
"$schema": "https://json-schema.org/draft/2020-12/schema"
}🟡deconetwork_add_order_note(order_id, content, order_line_id)
WRITE: add an INTERNAL note (visible to staff, not sent to the customer) to an order, or to one line item with order_line_id. Each call adds a new note, so do not repeat it. POST /api/json/manage_orders/add_internal_note.
Esquema de entrada
{
"type": "object",
"properties": {
"order_id": {
"type": "string",
"minLength": 1,
"maxLength": 100,
"description": "The order's invoice number, e.g. INV1234 (this is the order id)."
},
"content": {
"type": "string",
"minLength": 1,
"maxLength": 5000,
"description": "The note text."
},
"order_line_id": {
"description": "Attach the note to this line item instead of the order.",
"type": "integer",
"exclusiveMinimum": 0,
"maximum": 9007199254740991
}
},
"required": [
"order_id",
"content"
],
"$schema": "https://json-schema.org/draft/2020-12/schema"
}Comunidad
Evidencia