An external client can find a permitted customer, preview exact invoice totals and prepare a draft in Pepper. A person reviews the draft in Pepper and can issue it there. With a separate grant, the client can also issue one prepared invoice after that person approves the request in Pepper. Sending the invoice and recording its payment are separate requests that also need the person's approval.
No AI account is required. A script or internal business tool can use the same access. If you connect a model-based client, that client's data handling is a separate choice.
Three bounded jobs
An optional client can prepare an invoice draft, explain overdue balances or show customer context. You confirm invoice issuance. Balances come from Pepper’s exact calculations; contacts, activity and files stay within current permissions and granted scopes. Open the returned links to check the records yourself.
MCP Inspector 2.10.1 and FastMCP CLI 4.1.0 completed all three scripted jobs over HTTPS with synthetic records and no model calls. The AI-client manual gives connection steps and example requests. No other client or model behavior is claimed as tested.
The audit log records actions and sampled reads. Installation health includes audit integrity among its checks.
Grant access to the work it needs
Access starts off. The owner enables agent connections and creates an expiring grant for a staff member's permitted work. The selected capabilities limit what the client can do; the staff member's current permissions and record access also apply.
Connections expire after 1 to 30 days. The owner can revoke a connection or turn access off. Keep the credential in a server-side secret store. HTTP calls require HTTPS and do not accept browser JavaScript. MCP clients can also use browser OAuth sign-in.
Begin with read and preview access when evaluating a client. Add draft creation or updates when you have checked how it selects the customer, tax rate and currency.
Make the review useful
Give the client a concrete instruction, such as preparing a USD 250 draft for two units of an agreed service at USD 125 each, with the intended dates and tax treatment. Open the saved record and compare it with the agreement.
Check the customer as well as the total. A mathematically correct invoice for the wrong customer is still wrong. Review the descriptions, quantities, price, currency and dates before issuance.
Pepper calculates the monetary result on the server. The client sends exact values, not a model's estimated total. Writes use retry keys to avoid creating a second draft when the same request repeats. A stale update leaves the draft unchanged and needs review against the latest record.
Keep the released boundary clear
A separately granted issue request needs the delegated person's approval of one document in Pepper. Approval expires 10 minutes after preparation unless the owner sets another window. The client must execute the approved request before expiry; approval alone does not issue the invoice. Sending, recording a payment, exporting and changing bank or tax settings work the same way: each runs only after the person approves the exact change. See Approve sensitive steps. Pepper also offers an optional built-in Assistant, with its own personal grant and a confirmation before every write.
Revoking access stops later calls. It cannot remove a copy the client already made. Decide which permitted information the client may send to a model or another service, and read that service's terms before connecting it to business records.
Start with the developer guide to plan the requests, limits and retry behavior. The connection manual and API reference explain MCP, browser sign-in and the separate approval workflow. Consult the changelog for release history.