Precoro MCP by usefulapi
Server Details
Read Precoro purchase orders, invoices, suppliers and budgets; approve, reject and submit documents.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 24 tools
Each resource has a clear list/get pair, and descriptions explicitly delimit them (e.g. 'Line items come only from precoro_get_purchase_order'), so agents can pick correctly. Minor overlap remains between the generic approve/reject/submit_document tools (which operate polymorphically across document types) and the per-resource tools, and precoro_list_reference_data is a broad catch-all for many config tables, but neither causes real misselection.
Every tool uses the same snake_case verb_noun pattern with a uniform precoro_ prefix: list_/get_/create_ plus approve_/reject_/submit_document. Resource nouns are used identically across list and get variants (purchase_orders, purchase_requisitions, receipts, invoices, expenses, suppliers, items).
24 tools is on the heavy side of the rubric's comfortable range, but the domain genuinely spans requisitions, POs, invoices, expenses, receipts, suppliers, items, payments, budgets, contracts, AP inbox and reference data, each needing at least read access. The set is not padded with redundant variants.
Read coverage is thorough and the approval lifecycle (create draft, submit, approve, reject) is present for requisitions and suppliers, but creation is missing for most document types (purchase orders, invoices, expenses, receipts) and there is no update or delete operation anywhere (e.g. no way to edit a supplier or item). Agents can work around some gaps via the AP inbox OCR flow, but several lifecycle steps are dead ends.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Read Bokio accounts, invoices and customers; create drafts and journal entries.
Read team, time off, expenses and invoices; approve or decline time off and expenses in Oyster.
Read Breathe HR employees, absences, sickness and leave; create and review leave requests.
Read invoices, clients, suppliers and cashbook; create invoices and clients in Fatture in Cloud.
Related MCP Servers
- 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
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to query and manage ERP procurement data, including suppliers, parts, inventory, and purchase orders, with human approval for write operations.-
- FlicenseNot gradedqualityDmaintenanceManages agentic workflow spend through budget quotes, policy gates, approvals, receipts, and cost evidence exports.-
- AlicenseAqualityDmaintenanceEnables interaction with Brex financial data including expenses, budgets, transactions, and accounts through read-only API access with support for pagination, filtering, and receipt management.2123 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.