Use Pepper from your AI client

For: people who want to get work done in Pepper through their own AI app.

Your AI works within your access and approval choices. Everyday changes can save immediately. Sensitive work needs your decision or a matching rule.

First, connect your AI app and choose its access.

Your app interprets your request. Pepper checks permissions and calculates every amount. It works without an AI account if you prefer the dashboard.

Choose a job

Try one of these requests. The app needs the listed work’s access, and its wording can differ. Owners can inspect jobs under Settings > Agent connections > Jobs.

You can name a customer, document, lead or task in your request. The app can look up the record without asking you for its ID.

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.
Qualify a lead	“Qualify the lead from Portside Press into a deal called Website redesign.”	The existing customer, its primary contact and an open deal. The lead closes as qualified. Nothing is quoted or sent. A new customer needs your approval first.
Prepare a quote for a deal	“Create a quote for website design for Portside for 2,000 euros.”	An editable quote draft with exact totals, linked to the deal. Issuing needs your approval in Pepper.
Review the pipeline	“What is in the pipeline this month, and which deals have gone quiet?”	Open and weighted pipeline per currency, won and lost in the period, and the stale deals with their reason. No deal changes.
Report on analytics	“How did last month go, and what changed against the month before?”	Totals, each section's answer with its proof, the change against the previous period, and the records behind a result. Nothing changes.
Log time	“Log 2 hours on WEB-130 for today.”	A time entry on a permitted task, with the rate resolved by Pepper.
Show project status	“Show the progress, unbilled work, budget and margin for Acme.”	Project figures within the delegated person’s access, with their calculation bases.
Invoice unbilled time	“Invoice the unbilled time for Acme this month.”	A reviewable invoice draft from the selected time. Issuance needs your confirmation.
Send an issued invoice	“Email invoice INV-2026-0041 to Acme's billing contact.”	An approval request that shows the recipients, subject and text. The email goes out after you approve it.
Record a payment	“Acme paid EUR 344.85 by bank transfer today.”	An approval request with the exact amount and the new balance. The payment is recorded after you approve it. No money moves.

The Sales tools and project tools describe the additional jobs, required grants and limits.

Open the returned record link to check the result in Pepper. The screen and tool use the same records, permissions and 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

Each client completed its tests against a disposable HTTPS installation with a verified certificate. The tests used synthetic records and no model calls.

Client	Tested version	Date	What the test covered
MCP Inspector	2.10.1, Node.js 22.21.1	13 October 2026	Invoice, overdue-balance and customer-context jobs; a pasted credential; browser sign-in, consent and token refresh
FastMCP CLI	4.1.0, Python 3.12.14	13 October 2026	Invoice, overdue-balance and customer-context jobs with a pasted credential
MCP TypeScript SDK client	1.32.1, Node.js 22.21.1	21 October 2026	Browser sign-in and consent; the full tool list in pages and `search_tools`; prompts and resources; one change prepared, approved in Pepper, run and retried with the same key

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.

Issuing or emailing an invoice, recording a payment, exporting a report and changing bank or tax settings require approval. Other permitted changes can save at once. Check the access reference for each type of work.

Decide on the request in Pepper, or set a supported rule with limits. Approval alone does not complete the action. See Approve sensitive steps.

Each tool follows the same permissions as the dashboard. Activity records name the connected app and responsible person. The tool reference lists the boundaries by app.

You can also use Pepper's optional built-in Assistant after the owner configures a hosted provider. It uses a person's separate tool grant and starts at Ask every time. You can allow routine work or set approval rules with limits. External clients keep the access and approval rules described here. Client and model subscriptions, if needed, are separate.

Check what happened

Open the record link returned by your app to check the saved result. Open Connect your AI > Agent approvals to review a pending request.

Under Your connections, choose Stop to block an app’s new requests. Saved work stays in Pepper. Owners can inspect saved drafts and approval states under Settings > Agent connections > Connected clients.

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.