ap-agent MCP server
Related Servers
Alternatives to ap-agent MCP server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceSelf-serve MCPB demo for accounts payable invoice exception review. It performs deterministic matching across invoice, purchase order, goods receipt, vendor master, invoice history, tax code master, and payment rules.-
- FlicenseNot gradedqualityCmaintenanceEnables accounts payable teams to extract invoice data from PDFs and images, detect duplicates, normalize vendor names, calculate payment terms, and validate invoice completeness. Supports local extraction for text PDFs and optional vision providers for scanned documents.-
- AlicenseNot gradedqualityBmaintenanceEnables converting invoice PDFs, scans, and photos into Excel/CSV spreadsheets, checking invoice arithmetic, extracting structured JSON data, and retrieving outputs from previously submitted documents through a hosted MCP service.297 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to search supplier invoices in a mock ERP, run three-way matching against purchase orders and goods receipts, and route failed matches to human approval.5242 npm1MIT
- 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
- AlicenseCqualityDmaintenanceEnables managing invoice workflows using Temporal, allowing submission, approval, rejection, and status checking of invoices through MCP tools.421MIT
TDQS
Scored across 11 tools
Each tool targets a distinct resource plus action: listing vendors/bills/POs/inbox, a single-PO fetch, invoice validation, two distinct proposal creation paths (bill vs payment), proposal status, posting, and audit retrieval. The closest pair, check_invoice and propose_bill, is clearly separated by descriptions (read-only three-way match versus drafting for approval), so an agent can reliably choose.
All names use snake_case verb_noun form (list_vendors, get_purchase_order, propose_payment, post_approved_proposal) with consistent resource nouns across the set. Minor verb variety (check vs get/list) is semantically motivated rather than arbitrary, and no camelCase or style mixing appears.
Eleven tools is well within the ideal 3-15 range and each maps to a needed step in the accounts-payable workflow: discovery, validation, proposal creation, approval status, posting, and audit. There is no filler tool and no obviously missing sibling that would bloat the surface.
The core lifecycle is covered end to end: read vendors/bills/POs, validate an invoice, propose bill or payment, check proposal status, post an approved proposal, and inspect the audit trail. Gaps remain in read paths—no get_bill or bill-level detail beyond list_open_bills, and no list_proposals (only single-proposal lookup)—but agents can work around these via the proposal and audit tools.