< Back to all integrations

Oracle Fusion Cloud ERP

ERP & Finance

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 + engini ]

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.

MCPPython and TypeScript SDKCLIREST APIWorkflow Studio
CoversPayables invoices, receivables invoices, suppliers, purchase orders and requisitions
ToolsListed with their permissions in the engini Tool Catalog
GuideThe help-center guide is being written
[ 01 / What agents can do ]

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

Payables invoices

Supplier invoices in accounts payable.

Covered
Receivables invoices

Customer invoices in accounts receivable.

Covered
Suppliers

Supplier records.

Covered
Purchase orders

Orders to suppliers.

Covered
Requisitions

Requests to buy.

Covered

Triggers

Triggers for Oracle Fusion are not documented yet. A workflow can run on a schedule and read what changed.

[ 02 / Connect your agent ]

Connect your AI agent to Oracle Fusion Cloud ERP. Four ways in, one set of permissions.

MCP

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 →
SDK

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 →
CLI

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 →
REST API

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 →
MCP in four steps
In engini, connect Oracle Fusion Cloud ERP and create an MCP server with that connection and the tools this agent may use.
Claude: Settings, Connectors, Add custom connector, then paste the server address.
Cursor: add the address to .cursor/mcp.json. Claude Code: claude mcp add.
Sign in through engini when the client asks. The agent sees only the tools you chose.
Cursor, connected to Oracle Fusion Cloud ERP through engini
// .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.

Try asking your agent
“Which payables invoices from Acme are open?”
“What is the status of requisition 2231?”
“List purchase orders for Globex this quarter.”
“Which customers have overdue receivables invoices?”
“Show the supplier record for Initech.”
“Which requisitions are still not on a purchase order?”

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.

[ 03 / What teams build ]

What teams build on Oracle Fusion Cloud ERP. Agents and workflows, across systems.

Accounts payable

Invoices from the inbox

Supplier invoices that arrive by email are read and matched to the purchase order in Oracle Fusion.

OutlookOracle Fusion Cloud ERP
Procurement

Requests into requisitions

A purchase request from Teams or Slack becomes a requisition in Oracle Fusion.

Microsoft TeamsOracle Fusion Cloud ERP
Collections

Receivables on request

An agent in Claude answers which customer invoices are overdue. Its toolset holds read tools only.

Oracle Fusion Cloud ERPClaude
Revenue operations

CRM and ERP in step

Customer and invoice status from Oracle Fusion flows back to Salesforce.

Oracle Fusion Cloud ERPSalesforce

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.

[ 04 / Agent Policy ]

You decide what each agent may do in Oracle Fusion Cloud ERP. engini enforces it on every call.

Toolsets

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.

MCP servers

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.

Identity

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.

Credentials

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.

Audit

Every call on record

Every call lands in History and the audit log, which you can export or stream to your SIEM.

Environments

Test before production

Workspaces keep teams apart, and development, staging and production environments keep a test agent away from live data.

SOC 2 Type IIISO 27001GDPRSecurity at engini →
[ Good question ]

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.

[ 05 / Set up ]

Connect Oracle Fusion Cloud ERP in three steps. Then decide what each agent may do.

Step 01

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.

Step 02

Choose the tools

Add the connection to an MCP server or a toolset with only the tools each agent needs.

Step 03

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.

[ 06 / Questions ]

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.