Talk to your ERP.It writes back — in your books, on the record.

The life of one request

Five entries, one posting.

1. 01

   The ask

   You ask, in plain language, from Claude, Cursor, or ChatGPT — "mark this invoice as paid" or "which customers are overdue past 60 days?"

2. 02

   OAuth 2.0 + PKCE

   The model signs in as a real user — Authorization Code flow, dynamic client registration, automatic token refresh.

3. 03

   Your roles, your rows

   Every tool call is scoped to that user's Frappe and ERPNext permissions. Can't see it in the Desk? Can't see it through FAC.

4. 04

   The approval gate

   FAC Chat only

   A human with the right role can review a write before it lands, and approve or reject it. This gate is a FAC Chat feature — over the open-source MCP server, this step doesn't run: a write executes immediately, inside the caller's Frappe permissions (see the tool index below for exactly which calls mutate data).

5. 05

   Assistant Audit Log

   Caller, tool, arguments, result — every call posted to the record. The books balance because nothing skips the journal.