AI agents

How to connect your ERP or software to an AI agent

Most business software already has an API. An AI agent can use that API to read data and draft work, the same way a careful new employee would. What makes it safe is the plumbing around it: what the agent may see, what it may change, and who checks it.

Three ways to connect

No.PointWhat it means in practice

01Direct API toolsWe give the agent a small set of tools that call your ERP's API: find a customer, list overdue invoices, draft a quote. Simple, fast and easy to audit.

02MCP serverThe Model Context Protocol is an open standard for connecting AI assistants to software. An MCP server for your ERP lets Claude and other assistants use it through one consistent interface.

03Inside the ERPThe agent lives inside the ERP as a user staff can message, with its own permissions and an approval queue. This is how we connect Odoo.

The rules we always build in

No.PointWhat it means in practice

01Least accessThe agent gets its own login with only the permissions it needs, never an admin account.

02Drafts, not actionsAnything that changes money, stock or a customer goes to a person for approval.

03Your account, your dataThe AI runs on your own account and keys, so data and costs stay with you.

04A full logEvery request, tool call and answer is recorded.

Which systems

Odoo, QuickBooks Online, Xero, Zoho Books, NetSuite and most custom software with a REST or JSON API. Where a system has no API, we build a small one first.

Questions people ask

What is an MCP server?

A small service that describes your software's actions to an AI assistant in a standard way, so the assistant can use them safely. We build them for ERPs and internal tools.

Do we need to change ERP?

No. The agent connects to the system you already use.

How do we start?

Pick one job that wastes time every week, such as chasing overdue invoices. We connect the agent for that job first, then add more.