> For the complete documentation index, see [llms.txt](https://help.supplyd.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.supplyd.co/mcp/what-you-can-do/available-information.md). # Available information The ERP information available through Supply'd MCP. {% hint style="info" %} MCP is a read-only private beta for invited Supply'd ERP customers, not standalone Hub or Lite accounts. {% endhint %} ## Current capabilities There are 13 tool areas. A tool can support several operations, such as searching records and opening their details. You can ask in ordinary language; you do not need the tool names. | Area | Available information | | ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | | Company | Company profile, locations, departments, integrations and tax rates | | Customers | Customer search, details and order history, with date and status filters | | Deliveries | Deliveries, delivery runs and delivery orders, including their details | | Fulfilment | Search fulfilments and read picking, packing and line progress | | Inventory | Stock for a product, inventory records, batches and inventory activity scoped to a product, inventory record or batch | | Products | Product search and details, related recipes, substitutes, suppliers, sales channels, demand and production methods | | Production | Search production runs, view product production history and open individual runs | | Purchases and expenses | Search purchase orders, find the latest order, view product purchase history and outstanding items, and open orders or expenses | | Reports | Authorised business summaries across sales, margins, purchasing, production, inventory, write-offs, deliveries, pick-and-pack, tasks and customers | | Sales | Search orders, view product sales history, and open order or invoice details | | Suppliers | Supplier search and details | | Tasks | Task search, details and templates | | Help | Search Supply'd guidance and workflow documentation | ## Recipes and production methods Where recorded, product information includes ingredient quantities and their stage assignments, packaging, stage sequence, instructions, labour time and processing time. Related recipes and substitutes help you explore connected products without assuming that similarly named records are the same product. ## Expense reconciliation Expense details can compare three sources: * the original purchase-order lines; * the raw scanned invoice values; and * the saved expense values. The comparison can include line differences, totals, adjustments and unmatched lines. Ask the assistant to distinguish a scanned value from a saved value and to identify the records behind a discrepancy. Missing source data cannot be reconstructed by MCP. ## Connected questions For example, find a product by SKU, read its recipe and stage timings, then retrieve its production history, recent sales or inventory activity. Each retrieval may be a separate server call. The client should reuse returned record references. If a name matches several records, provide the exact SKU or record reference before continuing. ## Access varies by user This catalogue describes supported capabilities, not a grant of access. Results depend on the connection's selected business areas, your current ERP permissions, company configuration and available records. See [Reports and help](/mcp/what-you-can-do/reports-and-help.md) and [Limits and expected behaviour](/mcp/what-you-can-do/limits-and-expected-behaviour.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.supplyd.co/mcp/what-you-can-do/available-information.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.