F
licenseNot graded
qualityD
maintenanceEnables AI agents to query and manage ERP procurement data, including suppliers, parts, inventory, and purchase orders, with human approval for write operations.
-
erp-mcp
Related Servers
Alternatives to erp-mcp
No user-submitted related servers found.
Related Servers
- 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
- 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-
- AlicenseAqualityCmaintenanceEnables AI assistants to raise, submit, approve, amend, and cancel purchase orders and onboard suppliers in ERPNext or SAP S/4HANA while enforcing procurement controls such as duplicate detection, budget limits, split-purchase checks, price tolerances, and segregation of duties.14MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to query and operate on ERP data through a unified tool interface, working across CSV exports, SFTP drop folders, SQLite/ODBC, and optional enterprise APIs. It supports purchase orders, vendors, and inventory lookups while keeping agent-facing tools consistent regardless of backend.MIT
- AlicenseAqualityBmaintenanceEnables an LLM agent to read from and propose changes to a financial ERP, executing writes only after human confirmation delivered through the channel, with role checks, risk tiers, audit logging, and a master kill-switch.101MIT
TDQS
A3.5/5.0
Scored across 4 tools
Disambiguation5/5
Each tool targets a distinct resource and action: vendor search, PO listing, single PO retrieval, and invoice posting. There is no overlap between listing purchase orders and getting one order, since one is scoped per-vendor and the other per-document.
Naming Consistency5/5
All four names follow a strict verb_noun snake_case pattern (search_vendors, list_purchase_orders, get_purchase_order, post_vendor_invoice). Verbs are well chosen and consistently distinguish read vs. write operations.
Tool Count4/5
Four tools is on the lean side but each supports a step in the vendor-invoice workflow, so nothing is redundant. A slightly broader surface (e.g. retrieving posted invoices) would make the set feel less minimal.
Completeness4/5
The core workflow — find vendor, inspect open PO amounts, read a PO, then post/preview an invoice — is fully covered, including idempotency. Minor gaps remain: no way to list or fetch invoices by vendor/reference outside of a repeat post, and no vendor-detail retrieval.
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues