ERP Procurement MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ERP_DATA_FILE | No | Absolute path to a JSON data file with the same shape as the bundled sample data. Optional; the server uses the sample data by default. | |
| APPROVALS_API_URL | No | URL of the approvals platform. When set together with APPROVALS_API_EMAIL and APPROVALS_API_PASSWORD, approval requests are sent to its exception queue instead of staying in memory. | |
| APPROVALS_API_EMAIL | No | Email of an approvals platform account with the agent role. | |
| APPROVALS_API_PASSWORD | No | Password for the approvals platform agent account. | |
| ERP_PRICE_TOLERANCE_PCT | No | Price tolerance percentage used in three-way matching. Defaults to 2 (i.e., ±2%). | 2 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_invoicesA | Lists supplier invoices from the ERP, soonest due first. Filter by status, supplier (id or part of the name) and due date. Use it to find invoices to check before payment. |
| get_invoiceA | Returns one invoice with its lines, the supplier, the purchase order it bills and the goods receipts for that order. |
| match_invoiceA | Checks an invoice against its purchase order and goods receipts: supplier, currency, duplicate invoice number, lines on the PO, unit price within the tolerance set by finance, quantity ordered and quantity received. Returns "matched" or a list of exceptions. |
| request_approvalA | Sends an invoice that failed three-way matching to a person for approval. Only received or on-hold invoices with exceptions are accepted. Calling it again for the same invoice returns the pending request instead of creating a second one. |
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 4 tools
Each tool targets a distinct step of the invoice workflow: listing/filtering, fetching a single invoice with its lines, performing the three-way match, and escalating a failed match. The only near-neighbours (get_invoice vs match_invoice) are clearly separated by 'returns data' versus 'returns matched/exceptions'.
All four tools follow the same snake_case verb_noun pattern: search_invoices, get_invoice, match_invoice, request_approval. The verb choice is also semantically precise (search for filtered lists, get for single-record retrieval).
Four tools is on the thin side but each covers a real step of the invoice-checking workflow, with no filler. A slightly broader surface (e.g. approval status) would justify a higher count, but nothing here is redundant.
The read and match flow is complete, but request_approval is a dead end: there is no tool to view pending approvals, approve/reject, or record payment/update status. An agent can start the approval loop but cannot close it without another system.