AI connections for Made with Pepper.
Control Pepperwith the AI tool you already use.
Use your existing AI tool, like Claude or ChatGPT, to control most features in Pepper. Manage customers, projects, invoices, bookings and more.
Connect a compatible AI app like ChatGPT or Claude, or enable Pepper’s built-in Assistant with your own Anthropic, OpenAI or OpenAI-compatible provider. Every app works without AI.
Ask your AI client
YouAdd Clay Hours as a lead from their website enquiry.
leads_createDone
AI clientClay Hours is a new lead. Their enquiry about an exhibition website is its message, and the original form response stays attached.
In Pepper
YouStart a website for the Portside Print Fair with the Studio layout.
websites_create· studioDone
AI clientA private draft with the Studio pages is saved. Nobody can see it until you approve publication in Pepper.
In Pepper
YouAdd Portside’s print editions to the catalogue with their prices and stock.
items_create· one call per editionDone
AI clientThe editions are in the catalogue with their variants, prices and stock, ready for a shop or a buy button on the website.
In Pepper
YouInvoice Kindred’s unbilled time this month and issue it.
engagements_prepare_invoiceDonedocuments_issue_prepareWaits for your approval
AI clientThe draft is saved from the tracked hours at Pepper’s rates. It has no number yet; issuing waits for your approval in Pepper.
In Pepper
Example records in real product screens. The tool names are real MCP tools of this release.
From a request to a real record
What can an AI assistant do in Pepper?
A compatible AI app can request actions on Pepper’s existing records. Pepper checks access, calculates amounts and saves permitted changes to the records your team uses.
“Prepare an invoice for Northwind Studio: three days of design at €500 a day.”
Before saving, confirm the customer, dates, currency and tax choice. This example shows €1,500 before any selected tax.
Illustrative workflow; not a recording of a tested chat session.An editable €1,500 invoice draft, before any selected tax. No invoice number. Nothing sent.
Review the customer, dates, lines and tax in Pepper. Approve finalising and numbering the invoice. Emailing it is a separate action.
Review and issue the draft
Review · Approval requested. Check the exact invoice in Pepper. Approval permits the AI app to issue it; the invoice is still a draft.
Issue · Invoice issued. After successful execution, the invoice has its assigned number. Check that result to confirm issuance. Nothing has been emailed.
Tools behind this request
customers_search → documents_preview → drafts_createRead inputs and permissions More tasks your AI app can handle
Use the customer, project and time records already in Pepper to prepare the next piece of work. Available actions depend on the connection’s access and the staff member’s permissions.
Customers & sales
Find customer details and past work, assess new enquiries, prepare quotes and check open sales opportunities.
Projects & everyday work
Update project tasks, record time and check unbilled work.
Invoices & money
Prepare invoice and quote drafts, check unpaid balances and read reports. Emailing documents, recording payments and exporting reports require approval.
Websites & customer services
Create and save private website drafts. Request approval for publication or restoration, prepare widgets and read permitted customer responses. Edit saved Web App source with a separate builder grant. Ask a person to review publication.
Settings & oversight
Check Pepper’s service-health results and see who changed records. Request supported settings changes or report exports for approval.
See every available action, the access it needs and whether it requires approval.
Open the complete tool referenceYou decide what can happen
Which changes need my approval?
Changes saved immediately.
With the required access, an AI app can save drafts, update tasks and log time immediately. Some deletions also happen immediately, including deleting editable time entries and moving files to the bin.
Review the exact change
Actions such as finalising an invoice, emailing it, recording a payment or exporting a report require approval of the exact request. Review its amounts, recipients and other proposed changes in Pepper.
Check that it completed.
After approval, your AI app must complete the action before the request expires. Changes to the record or access can prevent completion. Check the result to confirm it happened; retrying the same completed request does not repeat the change.
The connection acts for the person who connected it, within its granted access and that person’s permissions. When an action requires approval, the request goes to that person. They can approve it or set a rule with limits for supported actions.
See which changes need approvalFor invoice approval, the default window is 10 minutes from preparation. The owner can change it; approval does not restart the clock.
Connect when you’re ready
How do I connect my AI assistant?
Compatibility and connection limits
Published tests cover MCP Inspector, FastMCP CLI and an MCP TypeScript SDK client using synthetic records without model calls. They do not establish ChatGPT, Claude or other chat-app workflows. Check the tested versions and your app’s remote MCP support before connecting.
- Open Connect your AI.Click your name in Pepper and choose Connect your AI. On a phone, open More first. If AI connections are off, the owner turns them on on the same screen. Guests cannot connect an app.
- Add Pepper’s address to your AI app.Copy the address and follow the steps for Claude, ChatGPT, Codex or another app that supports remote MCP. Pepper needs HTTPS and the correct application address.
- Sign in and choose the access.Select only the access the app needs and an expiry of 1 to 30 days. The app works as you and cannot exceed your permissions. Stop it on the same page at any time.
Browser sign-in requires Pepper at the root of an HTTPS domain or subdomain; it does not support a subfolder installation.
Follow the connection guideA deliberate choice
What business data does my AI provider receive?
Your connection controls what it can retrieve.
Pepper runs on hosting you choose. It returns only information permitted by the connection’s access and the staff member’s permissions. If your AI app sends that information to a cloud provider, the provider receives it under its own terms.
You can close the connection.
Disconnect at any time to stop future requests. This cannot remove copies already held by the AI app or provider. Pepper checks access on every request and identifies the staff member and connection in each record’s change history.
Some steps always stay with people.
People handle passwords, two-factor sign-in, connection setup, approvals, software updates and backup download or restore in Pepper. An AI connection cannot give consent, make a booking or claim an offer on a customer’s behalf.
See what an AI connection cannot doFor developers.
Connect through Pepper’s MCP server or HTTP API.
Pepper’s MCP server and HTTP API use the same business actions, permission checks and calculations. Actions that require approval follow the same approval process through either interface.
Model Context Protocol
tools/list · prompts/list · resources/readDiscover allowed actions and their input and output formats, use workflow templates, and retrieve permitted records. MCP exposes these as tools, prompts and resources.
HTTP API
GET /api/v1/toolsCall Pepper’s actions from your server or command-line integration and receive structured results and errors. You can use the HTTP API without an AI model.
The details that make integrations dependable
- Discover before calling
- Read the actions available to this connection and their required inputs and returned fields. Search Pepper’s records to obtain the IDs each action needs.
- Keep amounts exact
- Pepper calculates stored totals. Use each amount’s documented currency and scale: for example, an invoice unit price of “10001” means EUR 100.01. Keep different currencies separate. Invoice input specification
- Retry without duplicating work
- Give each change a request identifier—an idempotency key—and reuse it when retrying that same change to avoid duplicates. Out-of-date approvals need a new request and review.
- Follow the result
- Use returned record links to check results and structured errors to handle failures. Instructions found inside customer records must not authorise extra access or change the task.
Explore Pepper or connect
your existing installation.
New to Pepper? Inspect its customer, project and invoice records in the read-only demo, then check pricing and hosting requirements. Already running Pepper? Follow the connection guide and test changes on a separate installation.
Hosting and email cost extra. You or your technical partner handle hosting, updates and backups.