Skip to main content
Glama
ap-agent MCP server

ap-agent MCP server

by Icandi40

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AP_AGENT_LEDGERNoSet to "qbo" to switch the ledger to the QuickBooks Online sandbox; otherwise the offline stand-in is used.
AP_AGENT_RECEIVING_LOGNoPath to a CSV receiving log with columns po_number,sku,qty_received,received_date.
AP_QBO_BANK_ACCOUNT_IDNoQuickBooks Online checking/bank account id to use for the sandbox company.
AP_QBO_EXPENSE_ACCOUNT_IDNoQuickBooks Online expense account id to use when posting bills to the sandbox company.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

You are an accounts payable assistant working inside the company's books (a sandbox). For each invoice: call check_invoice, explain the outcome and any flags in plain words, then call propose_bill. You cannot approve anything. Tell the person the proposal id and that it is waiting in the review page. After they approve it, call post_approved_proposal. Never ask for or repeat bank account numbers, card numbers, or passwords.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_vendorsA

List active vendors in the system of record.

list_open_billsA

List bills with an unpaid balance, optionally for one vendor.

list_purchase_ordersA

List purchase orders. status is Open or Closed; pass an empty string for all.

get_purchase_orderB

One purchase order with its lines and what the receiving log says arrived.

list_inboxC

Invoice files waiting in the inbox folder.

check_invoiceA

Extract fields from an invoice (pasted text, or a file in the inbox) and run the three-way match against the PO and receiving log. Writes nothing to the ledger.

propose_billA

Draft a bill from an invoice and queue it for human approval. Does NOT post it.

propose_paymentA

Queue a scheduled payment of an open bill for human approval. Does NOT pay. pay_date is YYYY-MM-DD. Uses the sandbox company's own bank account reference.

get_proposalB

Status of a proposal: pending, approved, rejected, executed or failed.

post_approved_proposalA

Write an APPROVED proposal to the system of record. Refuses unless enough people approved it and the payload is unchanged since they did.

get_audit_trailB

Every audit log entry for a proposal and the invoice behind it.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 11 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues