Main
Start with a read-only set of ERP use cases (search, list, reports) before enabling update/delete tool calls.
Use OAuth scopes/roles to enforce least privilege: create a dedicated ERP user for the assistant.
Turn on audit log review as a routine: treat tool calls like API access and monitor unexpected queries.
If you extend tools from your own Frappe apps, keep them small and permission-scoped to your DocTypes.
README (excerpt)
Frappe Assistant Core
Talk to your ERPNext site. FAC lets Claude, ChatGPT, and other MCP-ready LLMs work directly with your invoices, customers, stock, workflows, and custom apps — inside your ERPNext permissions, with every call logged.
What you get
Once FAC is installed, your team can ask an LLM for things they'd normally do by hand:
"Show me overdue invoices from our top five customers."
"Update this lead's status to Qualified and set next action date to Monday."
"Run the monthly revenue report and summarise the top movers."
"How much stock of SKU-1234 do we have across all warehouses?"
Behind that simple interaction, FAC exposes 24 built-in tools for the things your team does every day — document CRUD, search, reports, workflows, analytics, file extraction, and dashboards. Admins can publish Skills (reusable instructions that teach the LLM how to
Source-backed notes
- README describes connecting MCP-ready clients to an ERPNext site and authenticating via OAuth 2.0 (PKCE).
- README lists a self-hosted install path via
bench get-app ...andbench --site <your-site> install-app .... - README states FAC ships 24 built-in tools across plugins (documents, search, reports, analytics, dashboards).
FAQ
- Does it work with self-hosted ERPNext?: Yes—README includes a bench-based install path for self-hosted deployments.
- How is access controlled?: README describes OAuth-based user authentication and ERP role-based permissions.
- How do I keep it safe?: Start read-only, use a dedicated user, and review audit logs regularly.