MYOB
Connect AI agents and workflows to MYOB Business and AccountRight: customers, suppliers, items, invoices, bills, payments, accounts and journals.
Book a demo
MYOB for AI agents and workflows.
engini lets your AI agents and workflows work in MYOB, the accounting and business system used by companies across Australia and New Zealand: read customers, suppliers, items and accounts, enter sales invoices and bills, record payments, post general journals, read balances, and start a workflow when records change. Subsidiaries on MYOB stay in step with headquarters on another ERP. 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 MYOB. Every tool is one you allow or leave out.
The MYOB 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 contacts and items.
Read sales invoices and supplier bills with what is owed.
Read payments received and made.
Read the chart of accounts and balances.
Write
Bill a customer or enter a supplier bill.
Record money in and out.
Post a journal.
Keep records current.
Any endpoint
Call any MYOB API endpoint, with the sign-in added for you.
Triggers
Invoices or bills added.
Payments recorded.
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 MYOB. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your MYOB 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 MYOB 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 MYOB 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 MYOB 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 MYOB through engini
{
"mcpServers": {
"engini-myob": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your MYOB 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 MYOB tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build on MYOB. Agents and workflows, across systems.
Australia and New Zealand on MYOB
A subsidiary on MYOB sends sales and journals to headquarters on NetSuite or Business Central, and both sides balance.
Store orders into MYOB
Paid Shopify orders become MYOB invoices with the payment recorded.
Bills from the inbox
A supplier bill from email is read by an agent and entered in MYOB.
Numbers on request
An agent answers what was billed, what is overdue and what tax is due. 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 MYOB and another system engini connects is available.
You decide what each agent may do in MYOB. engini enforces it on every call.
Only the tools you allow
A toolset lists the MYOB 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 MYOB account and engini acts as that person, with their MYOB 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 MYOB in three steps. Then decide what each agent may do.
Sign in to MYOB
Add a MYOB connection, sign in with MYOB and choose the company file. Use a user whose role covers only what the workflows need.
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 MYOB from Claude, ChatGPT, Cursor or your own code.
MYOB and engini. Straight answers.
Can an AI agent write to MYOB, or only read?
Both. engini has tools to create invoices and bills, record payments, post journals and create and update customers, suppliers and items. 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 the agent act as me in MYOB?
It acts as the MYOB user who signed in, with that user's access to the company file. Every run is recorded under the person who started it.
Can a change in MYOB start work?
Yes. Scheduled triggers check MYOB for new invoices, bills and payments. A workflow can include an AI agent step.
What if the tool I need is not listed?
Use Send API Request to call any MYOB API endpoint through the same connection, and give it only to the agents that need it.