Payables MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AP_PROFILE | No | Controls which tools are registered when the server starts. Possible values are 'analyst', 'processor', or 'full'. If not set, the server likely runs in full mode. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_billB | Fetch one bill by id, with its total and status. |
| search_billsB | List bills, optionally filtered by status and vendor. |
| get_vendorC | Fetch one vendor by id. |
| create_billA | Create a bill. Bills over 25,000 ask the user to confirm first. |
| update_vendor_bankB | Record a change to a vendor's bank details. The vendor is frozen until someone confirms it in the ERP. |
| check_duplicatesB | Check a bill against the vendor's earlier bills. A match sets the bill to exception. |
| match_invoiceA | Match a bill against its PO and goods receipt. Returns matched, exception or no_po. |
| recommend_approvalA | Recommend approve or hold for a bill, with the reasons. Does not approve anything. |
| request_payment_releaseA | Queue approved bills for a payment run. Someone releases the run in the ERP. |
| get_pending_releasesB | List payment runs waiting to be released. |
| read_audit_logB | Show the most recent audit entries. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| payment_run_review | Go through the bills due this week |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| bills | All bills |
| policy | Tolerance and screening settings |
TDQS
Scored across 11 tools
Most tools have clearly distinct roles (create/get/search bills, match against PO, check duplicates, recommend approval, release payments). The only potential confusion is between check_duplicates and match_invoice, both bill-validation steps, but their descriptions ('earlier bills' vs 'PO and goods receipt') clearly separate them.
All tools follow a consistent snake_case verb_noun pattern (get_bill, search_bills, create_bill, match_invoice, request_payment_release). No mixing of conventions or vague verbs; the pattern is predictable throughout.
11 tools is well-scoped for a payables/AP workflow. Each tool maps to a distinct step (bill CRUD, validation, approval recommendation, payment release, audit) and earns its place without redundancy.
Core bill lifecycle (create, get, search, validate, recommend, release) and audit are covered, but there is no update_bill/void, no vendor search or create (only get_vendor by id), and no explicit approve action. These are workable gaps for a controlled approval workflow but leave some dead ends.