ERPNext
Connect AI agents and workflows to ERPNext: customers, items, sales and purchase orders, invoices, stock and any DocType, with webhooks.
Book a demoERPNext for AI agents and workflows.
engini lets your AI agents and workflows work in ERPNext, the open-source ERP built on Frappe: read and write any DocType, from customers and items to sales orders, invoices and stock entries, submit and cancel documents, run reports, call server methods, and start a workflow the moment an ERPNext webhook fires. Frappe Cloud or your own server. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.
Cursor, your code
audit log
in engini
What your agent can do in ERPNext. Every tool is one you allow or leave out.
The ERPNext tools in engini, grouped by what they change. Read tools are safe to hand out widely. Write and delete tools go only to the agents that need them.
Read
Read any DocType with filters and the fields you choose.
Read master data and stock by warehouse.
Read billing and payables.
Run a query or script report.
Write
Write to any DocType you allow.
Move a document through its workflow, such as submitting a sales invoice.
Run a whitelisted server method.
Delete
Remove a draft document.
Triggers
An ERPNext webhook fires when a document is created, updated, submitted or cancelled.
Documents of a DocType changed since the last check.
A trigger starts a workflow, and a workflow can include an AI agent step. In Code, a trigger delivers the event to your own endpoint.
Connect your AI agent to ERPNext. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your ERPNext connection and only the tools you choose. Add its address to your client and sign in through engini. There is no key to copy.
MCP client setup →Python and TypeScript
Hand your agent a toolset of ERPNext tools. The SDK gives OpenAI and Anthropic models the tools in the format they expect and runs the ones they pick.
SDK guide →For coding agents
The engini CLI connects ERPNext and runs its tools from a terminal, with machine-readable output, so an AI coding agent can drive it without getting stuck.
CLI guide →Any language
Every ERPNext tool is an endpoint. Call it with exact inputs from a scheduled job or a sync, with no model in the loop.
API reference →.cursor/mcp.json. Claude Code: claude mcp add.// .cursor/mcp.json: Cursor, connected to ERPNext through engini
{
"mcpServers": {
"engini-erpnext": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your ERPNext connection and the tools this agent may use, then paste its address. The client signs in through engini on first use. Claude, VS Code and other clients take the same address: see the MCP client setup guide.
Each request runs through the ERPNext tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build on ERPNext. Agents and workflows, across systems.
Store and CRM orders into ERPNext
Orders from Shopify or HubSpot become ERPNext sales orders, submitted, with stock reserved.
Payments matched
Stripe payments are recorded as ERPNext payment entries against the right invoice.
Events that act
When a delivery note is submitted, the customer gets tracking and the account owner hears in Slack.
Answers from the ERP
An agent answers stock, order and invoice questions. Its toolset holds read tools only.
Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between ERPNext and another system engini connects is available.
You decide what each agent may do in ERPNext. engini enforces it on every call.
Only the tools you allow
A toolset lists the ERPNext tools an agent may call and the connection each one uses. Give one agent read tools only and another the write it needs. engini refuses any call outside the toolset.
Scoped when you set them up
An MCP server exposes only the connections and tools chosen when it is created, and engini shows who uses each server.
Whose permissions apply
Connect a person's own ERPNext account and engini acts as that person, with their ERPNext permissions. Use a shared integration account and it acts as that account. Every run is recorded under the user who started it.
Kept out of prompts
Your agent never needs your credentials: engini stores them and adds them when it runs each call, so keys stay out of prompts and tool inputs.
Every call on record
Every call lands in History and the audit log, which you can export or stream to your SIEM.
Test before production
Workspaces keep teams apart, and development, staging and production environments keep a test agent away from live data.
Connect ERPNext in three steps. Then decide what each agent may do.
Sign in to ERPNext
In ERPNext, generate an API key and secret for a user with only the roles the workflows need, then add an ERPNext connection with your site URL, key and secret.
Choose the tools
Add the connection to an MCP server or a toolset with only the tools each agent needs.
Build or ask
Use the connection as a step in a workflow, or ask your agent to work in ERPNext from Claude, ChatGPT, Cursor or your own code.
ERPNext and engini. Straight answers.
Can an AI agent write to ERPNext, or only read?
Both. engini has tools to create, update, submit, cancel and delete documents of any DocType you allow and to call whitelisted methods. Whether a given agent may use them is up to you: give it a toolset or an MCP server with read tools only, and it cannot call the rest.
Does it work with custom DocTypes and apps?
Yes. Get Documents, Create Document and Call Method work on any DocType and whitelisted method, custom apps included.
Frappe Cloud or self-hosted?
Both. engini connects to the site URL you give it, and to a self-hosted server inside your network through the On-Prem Agent.
Does the agent act as me in ERPNext?
It acts as the ERPNext user whose API key the connection uses, with that user's roles and permissions. Every run is recorded under the person who started it.
Can a change in ERPNext start work?
Yes. An ERPNext webhook can send any document event to engini, and scheduled triggers check any DocType for changes. A workflow can include an AI agent step.