ERP MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ERP_DB_PATH | No | Path to the ERP database file | |
| ERP_AUDIT_LOG | No | Path to the JSON Lines audit log file |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_stockA | Look up product stock levels. Use for questions like "How many cordless drills do we have?", "Which products are below reorder level?" or "Show stock for Safety Equipment". Returns stock quantity, reorder level, shortfall and units sold in the last 90 days. Results are sorted with the most critical stock first (max 50 rows). |
| get_order_statusA | Get the full status of one sales order. Use for "What's the status of order SO-1042?" or "Has SO-1509 been invoiced or paid?". Returns header (customer, dates, status, lateness), order lines, and the invoice with payments and outstanding amount. |
| get_customer_balanceA | Get a customer's account balance (accounts receivable). Use for "What is Oakhurst's open balance?", "Is C-0034 over its credit limit?" or before drafting a payment reminder. Returns contact details, credit limit, invoiced, paid, open and overdue amounts, each overdue invoice with days overdue, and counts of open/overdue orders. |
| list_overdue_ordersA | List sales orders that are late: promised date passed but not yet delivered. Use for "Which orders are late?", "Show orders more than 14 days late" or "Does Foxglove have any delayed orders?". Sorted by days late, max 50 rows, with total value of the late orders. |
| get_kpiA | Calculate a business KPI for a date range from a fixed list of metrics. Use for "How did revenue this quarter compare to last quarter?", "Top 5 products last month", "Average order value in 2026" or "How much is overdue?". Example: metric='revenue', period_start='2026-10-01', period_end='2026-12-31', compare_previous=true. Partial periods include a like-for-like comparison. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct ERP query area: order status, customer balance, overdue orders, stock, and KPIs. There is some possible overlap between get_order_status, list_overdue_orders, and get_kpi for overdue-related questions, but the descriptions clarify different scopes and outputs.
All names use consistent snake_case verb_noun structure: get_order_status, get_customer_balance, list_overdue_orders, get_stock, get_kpi. The use of get_ vs list_ is predictable and semantically appropriate.
Five tools is well-scoped for an ERP reporting/query server, with each tool covering a clear analytical need. There are no redundant tools and the surface feels appropriately focused rather than padded.
The surface covers key read-only ERP workflows: order status, receivables, overdue orders, stock, and KPI reporting. Minor gaps exist around broader lookup operations such as listing customers/products or searching orders, but core agent queries are covered.