Oracle Fusion Cloud ERP
Connect AI agents and workflows to Oracle Fusion Cloud ERP: payables and receivables invoices, suppliers, purchase orders and requisitions.
Book a demo
Oracle Fusion Cloud ERP for AI agents and workflows.
engini connects AI agents and workflows to Oracle Fusion Cloud ERP for the work finance and procurement teams do every day: payables and receivables invoices, suppliers, purchase orders and requisitions. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio, with each agent limited to the tools you allow.
Cursor, your code
audit log

in engini
What your agent can work with in Oracle Fusion. Every tool is one you allow or leave out.
The areas of Oracle Fusion Cloud ERP the engini connector covers. Each tool, and the permissions it needs, is listed in the Tool Catalog in the app.
Areas covered
Supplier invoices in accounts payable.
Customer invoices in accounts receivable.
Supplier records.
Orders to suppliers.
Requests to buy.
Triggers
Triggers for Oracle Fusion are not documented yet. A workflow can run on a schedule and read what changed.
Connect your AI agent to Oracle Fusion Cloud ERP. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your Oracle Fusion Cloud ERP 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 Oracle Fusion Cloud ERP 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 Oracle Fusion Cloud ERP 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 Oracle Fusion Cloud ERP 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 Oracle Fusion Cloud ERP through engini
{
"mcpServers": {
"engini-oracle-fusion-cloud-erp": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your Oracle Fusion Cloud ERP 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 Oracle Fusion Cloud ERP tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build on Oracle Fusion Cloud ERP. Agents and workflows, across systems.
Invoices from the inbox
Supplier invoices that arrive by email are read and matched to the purchase order in Oracle Fusion.
Requests into requisitions
A purchase request from Teams or Slack becomes a requisition in Oracle Fusion.
Receivables on request
An agent in Claude answers which customer invoices are overdue. Its toolset holds read tools only.
CRM and ERP in step
Customer and invoice status from Oracle Fusion flows back to Salesforce.
Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between Oracle Fusion Cloud ERP and another system engini connects is available.
You decide what each agent may do in Oracle Fusion Cloud ERP. engini enforces it on every call.
Only the tools you allow
A toolset lists the Oracle Fusion Cloud ERP 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 Oracle Fusion Cloud ERP account and engini acts as that person, with their Oracle Fusion Cloud ERP 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.
Oracle has its own MCP server. Why add engini?
Oracle, like other systems of record, now ships an MCP server for its own applications. It covers Oracle, which is enough when Oracle is the only system your agent touches.
Finance agents rarely stop at the ERP. The deal is in Salesforce, the invoice in an inbox, the bank file in an SFTP drop. engini connects the same agent to all of them, with one set of permissions and one audit log.
Connect Oracle Fusion Cloud ERP in three steps. Then decide what each agent may do.
Sign in to Oracle Fusion Cloud ERP
Add an Oracle Fusion Cloud ERP connection in the engini app with the credentials your Oracle administrator provides. Talk to us if you want help with the first setup while the guide is written.
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 Oracle Fusion Cloud ERP from Claude, ChatGPT, Cursor or your own code.
Oracle Fusion Cloud ERP and engini. Straight answers.
Can an AI agent write to Oracle Fusion Cloud ERP, or only read?
Both. the connector covers payables and receivables invoices, suppliers, purchase orders and requisitions; the Tool Catalog shows which tools read and which write. 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.
Is there a setup guide?
The help-center guide is being written. The Tool Catalog in the app lists every tool and the permissions it needs, and we can help with the first setup.
Is this the same as the Oracle Database connector?
No. Oracle Database is a separate connector for the database itself: rows, stored procedures and custom SQL.
Does the agent act as me in Oracle Fusion Cloud ERP?
It acts as the Oracle user behind the connection, with that user's roles in Oracle Fusion. Every run is recorded under the person who started it.