Oracle PeopleSoft
Connect AI agents and workflows to Oracle PeopleSoft HCM, Financials and Campus Solutions: run queries, read and update records through Component Interfaces.
Book a demo
Oracle PeopleSoft for AI agents and workflows.
engini lets your AI agents and workflows work in Oracle PeopleSoft, across HCM, Financials and Supply Chain, and Campus Solutions: run PeopleSoft queries, read employees, jobs, suppliers and vouchers, create and update records through Component Interfaces with all their edits, call Integration Broker services, and start a workflow when PeopleSoft publishes a message. PeopleSoft stays where it is, behind your firewall. 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 Oracle PeopleSoft. Every tool is one you allow or leave out.
The Oracle PeopleSoft 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
Run any PeopleSoft query the user can see, with its prompts.
Read people, positions and job history in HCM.
Read suppliers and payables in Financials.
Read purchasing in Supply Chain.
Write
Create or update a record through any Component Interface, with every PeopleSoft edit applied.
Change an employee's address, phone or emergency contact.
Enter payables and purchasing documents.
Call any REST or SOAP service published in Integration Broker.
Triggers
PeopleSoft publishes a service operation to engini, such as a new hire or a changed job.
A PeopleSoft query returns new rows.
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 Oracle PeopleSoft. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your Oracle PeopleSoft 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 PeopleSoft 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 PeopleSoft 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 PeopleSoft 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 PeopleSoft through engini
{
"mcpServers": {
"engini-oracle-peoplesoft": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your Oracle PeopleSoft 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 PeopleSoft 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 PeopleSoft. Agents and workflows, across systems.
New hires everywhere they need to be
When PeopleSoft publishes a new hire, accounts are created in Okta or Entra ID, a laptop is requested in ServiceNow and the manager hears in Teams.
Invoices into vouchers
A supplier invoice from the inbox is read by an agent and entered as a PeopleSoft voucher.
HR answers without a ticket
An agent in Teams answers time-off balance and pay questions from PeopleSoft. Its toolset holds read tools only.
Campus data where it is needed
Student and enrollment data from Campus Solutions reaches Salesforce and the data warehouse on a schedule.
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 PeopleSoft and another system engini connects is available.
You decide what each agent may do in Oracle PeopleSoft. engini enforces it on every call.
Only the tools you allow
A toolset lists the Oracle PeopleSoft 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 PeopleSoft account and engini acts as that person, with their Oracle PeopleSoft 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.
PeopleSoft behind your firewall.
If PeopleSoft runs in your own data center, install the engini On-Prem Agent on a server inside your network. It opens every connection itself: out to engini over HTTPS on port 443, and to PeopleSoft while it runs a task. You open no inbound ports or firewall rules. Calls through it run on the same engine as MCP, the API and workflows, and each one is recorded in History.
On-Prem Agent guide →Connect Oracle PeopleSoft in three steps. Then decide what each agent may do.
Sign in to Oracle PeopleSoft
In Integration Broker, activate the services the workflows need and give a PeopleSoft user permission lists for only those components, queries and services, then add a PeopleSoft connection with the gateway address and that user, through the On-Prem Agent if PeopleSoft runs inside your network.
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 PeopleSoft from Claude, ChatGPT, Cursor or your own code.
Oracle PeopleSoft and engini. Straight answers.
Can an AI agent write to Oracle PeopleSoft, or only read?
Both. engini has tools to create and update records through Component Interfaces, update personal data, enter vouchers and requisitions and call Integration Broker services. 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 write to PeopleSoft tables directly?
No. Writes go through Component Interfaces and Integration Broker services, so every PeopleSoft edit and security rule applies.
What if the tool I need is not listed?
Call Component Interface and Call Integration Broker Service reach any component or service your team publishes, and Run Query reads any query. Give them only to the agents that need them.
Does it cover HCM, Financials and Campus Solutions?
Yes. They share PeopleTools, Integration Broker and Query, so the same kind of connection reaches each one.
Does the agent act as me in Oracle PeopleSoft?
It acts as the PeopleSoft user behind the connection, with that user's permission lists and row security. Every run is recorded under the person who started it.
Can a change in Oracle PeopleSoft start work?
Yes. PeopleSoft publishes service operations to engini through Integration Broker as they happen, and scheduled triggers check queries for new rows. A workflow can include an AI agent step.