Use Pepper from your AI client

For: owners who want to use an external client with their Pepper records.

Before you start: use HTTPS and sign in as the installation owner. Follow Connect an external client.

AI is optional. Pepper needs no AI account or model provider. Your client interprets your request; Pepper checks permissions and calculates every amount. You confirm invoice issuance in Pepper.

Choose a job

Open Settings > Agent connections > Jobs to see the available work and its required access. These example requests describe supported tool sequences. A client's wording and model behavior can differ.

Job	Example request	Result
Prepare an invoice	“Prepare a EUR invoice for Northwind Studio: three days of design at EUR 500 per day.”	An editable draft with an exact EUR 1,500 total before any selected tax. No invoice number yet.
Explain overdue balances	“Which invoices are overdue, and how much remains unpaid?”	Current overdue invoices, their balances and record links. Totals stay separate for each currency.
Show customer context	“Show Northwind Studio's contacts, open documents, recent activity and files.”	The customer fields and records the delegated person can read. Each section also needs its corresponding connection grant.

Open the returned record link to check the result in Pepper. The screen and tool use the same records, permissions and PHP calculations.

An invoice draft can include customer details, dates, lines and your chosen tax rates. Review them before issuing it. A description alone does not establish a tax treatment.

Confirm an invoice

Preparing a draft does not issue it. If your connection has execution access, the client can request an approval link.

Open the review link in Pepper.
Check the customer, lines, dates, tax and exact total.
Approve that invoice if it is correct.
Return to your client to complete the approved request.

The approval applies to the reviewed invoice version. A changed, expired or revoked request cannot use it. A repeated execution request returns the same result without issuing twice.

Tested clients

These versions completed all three scripted jobs against a disposable HTTPS installation on 13 October 2026. The tests used synthetic records and no model calls.

Client	Tested version	Connection tested
MCP Inspector	2.10.1, Node.js 22.21.1	Streamable HTTP with a pasted credential; browser sign-in, consent and token refresh
FastMCP CLI	4.1.0, Python 3.12.14	Streamable HTTP with a pasted credential

These are MCP testing clients. This table does not claim tests of ChatGPT, Claude or another chat application's model-driven behavior. Check a client's support for remote MCP before connecting it.

MCP Inspector

Start MCP Inspector 2.10.1 in its web mode.
Add Pepper as a Streamable HTTP server.
Paste the address from Settings > Agent connections.
Start the connection.
Sign in to Pepper and review the requested access.
Allow only the access you need.
Return to Inspector and open Tools.

Inspector discovers Pepper's sign-in endpoints and manages its tokens. You do not paste an owner password into Inspector.

For a command-line client, use a private configuration file with a bearer credential from Advanced connection options. Keep that credential outside shared files and command history.

FastMCP CLI

FastMCP CLI uses a private MCP server configuration file. Set the server type to http, its url to Pepper's MCP address and its Authorization header to Bearer <credential>.

Use fastmcp list <config-file> to inspect the available tools. Use fastmcp call <config-file> customers_search --input-json '{"search":"Northwind"}' --json to find a permitted customer.

The tool reference defines the other inputs. MCP names use underscores, such as customers_context and invoices_receivables.

Understand the limits

The connection cannot read records or fields hidden from its delegated person. Removing access applies to later calls. A customer-read grant alone does not reveal invoices, activity or files.

Sensitive steps remain under human control. In this release, tools do not send invoices or email, record payments, delete business records, upload files or change bank settings. Form, board and widget proposals open in Pepper for your review and confirmation. The current tool and exclusion reference lists the boundaries by app.

Pepper has no embedded chat assistant in this release. Client and model subscriptions, if needed by your chosen client, are separate.

Check what happened

Open Connected clients to see saved drafts and recent approval states. Revoke a connection to stop its later requests and token refreshes.

Use Audit log to browse recorded actions and sampled reads, then verify the stored chain. Read sampling groups repeated access; it does not create one event per row.

Use Installation health to check the installation and follow the next action for a failed check. Audit chain integrity is one of those checks.