Supplyline MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUPPLYLINE_DATA | No | Path to a folder containing CSVs with the same columns as the sample data, used to supply your own data instead of the built-in sample dataset. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_partsB | Find parts by name, category, or part ID (for example "battery", "Display", or "P104"). |
| supplier_scorecardB | Lead time, quality (defects per million), on-time delivery rate, open and overdue POs, and sole-source parts for one supplier. |
| purchase_ordersA | List purchase orders, most late first. state is "open" (not yet received), "overdue", "late" (any PO that arrived or is running late), or "all". |
| bom_costC | Roll up the bill of materials cost for a product and show the biggest cost drivers. |
| supply_risksA | Rank parts by supply risk, with the reasons: single sourcing, stock that won't last through the lead time, overdue POs, and unreliable suppliers. Leave product empty to check every part. |
| simulate_delayA | What-if: if this supplier's shipments slip by N days, which parts and products could run out? |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| weekly_supply_review | A ready-made prompt for a weekly supply review of one product. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| products | The products in the dataset, one per line. |
TDQS
Scored across 6 tools
Each tool targets a clearly distinct supply-chain question: part lookup, supplier performance, purchase order status, BOM cost, risk ranking, and delay simulation. There is no meaningful overlap between tools, so an agent can select the right one directly from its purpose.
All names use consistent snake_case and are readable, but the convention is mixed between verb_noun (search_parts, simulate_delay) and compound noun phrases (supplier_scorecard, purchase_orders, bom_cost, supply_risks). This is a minor stylistic deviation rather than a confusing inconsistency.
Six tools is well-scoped for a supply-chain analytics server, with each tool covering a distinct analysis task. The surface is focused rather than padded or thin.
The set covers key workflows: finding parts, evaluating suppliers, tracking POs, rolling up BOM cost, ranking risks, and simulating delays. Minor gaps exist around direct inventory/stock queries and richer part or supplier detail, but agents can largely work around them through the existing tools.