ERP Procurement MCP Server
Related Servers
Alternatives to ERP Procurement MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables natural-language-driven purchase-to-pay workflows against mock procurement and payment APIs, including invoice matching, exception handling, human approvals, and idempotent payment scheduling with a tamper-evident audit log.MIT
- AlicenseAqualityBmaintenanceIt enables an LLM agent to list and inspect invoices, run three-way matches against purchase orders and goods receipts, and route exceptions under server-enforced policy.5MIT
- AlicenseBqualityBmaintenanceEnables AI models to three-way-match supplier invoices against purchase orders and goods received, returning deterministic approval, hold, or review decisions with human-readable reasons. It exposes tools to check invoices, list open purchase orders, and quote a plain-language matching policy, while never posting or paying anything.2MIT
- FlicenseAqualityCmaintenanceEnables an AI agent to handle accounts payable tasks against a mock ERP, including reading and writing bills and vendors, checking duplicates, matching invoices, recommending approvals, and queuing payment releases, with configurable profiles that limit available tools.11-
- AlicenseAqualityBmaintenanceEnables agents to search vendors, inspect purchase orders, and post vendor invoices through a guarded ERP REST API with preview-confirmed, idempotent writes and actionable errors.4MIT
- FlicenseBqualityBmaintenanceEnables AI agents to act as accounts-payable clerks in procedurally generated simulated companies by exposing tools to read inboxes, look up vendors and purchase orders, contact counterparties, request approvals, pay or reject invoices, and receive scored verifier results while keeping the answer key server-side.20-
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.