< Back to all integrations

Epicor Kinetic

ERP & Finance

Connect AI agents and workflows to Epicor Kinetic: customers, parts, sales orders, jobs, purchase orders and invoices, BAQs and Epicor Functions.

Book a demo
[ Epicor Kinetic + engini ]

Epicor Kinetic for AI agents and workflows.

engini lets your AI agents and workflows work in Epicor Kinetic: read customers, parts, sales orders, jobs and invoices, enter and change sales and purchase orders, run the BAQs your team built, call Epicor Functions, and start a workflow when a BPM or function sends a record. Manufacturers keep orders, production and the systems around them in step. Kinetic in the cloud or on premises. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.

MCPPython and TypeScript SDKCLIREST APIWorkflow Studio
Sign-inAn Epicor user and an API key, for the company you choose
ReachCustomers, parts, sales orders, jobs, purchase orders, invoices, BAQs and Epicor Functions
DeploymentEpicor cloud, or on premises through the On-Prem Agent
[ For on-premises customers ]

Moving off Epicor on premises? To Epicor cloud or the ERP you choose.

Epicor has announced a cloud-only roadmap: the last on-premises release is planned for 2028, with support through 2029. Every on-premises customer has a move ahead. engini connects to Epicor on premises where it runs today and to the ERP you are moving to, so you can load the new system, run both side by side and switch when the numbers match. We help you with the move, working with your team or your implementation partner.

Step 01

Connect Epicor on premises as it is

The On-Prem Agent reaches Epicor on premises, through its REST services and SQL Server database inside your network, with no inbound ports and nothing installed on the ERP.

Step 02

Map and check

An AI agent proposes how Epicor customers, parts, bills of materials, open orders, jobs and balances map to the new ERP and lists the records that would not load: missing fields, closed accounts, duplicates. Your team corrects the mapping before anything is written.

Step 03

Load in batches

Master data, open receivables and payables, balances and the history you choose move in batches. Every record is in History, so nothing is lost or loaded twice, and failed rows are retried.

Step 04

Run side by side, then switch

During the parallel run, new transactions in Epicor on premises sync to the new ERP on a schedule, so both sets of books match until the day you switch. Afterwards, agents can still answer questions from the Epicor on premises history.

Source: Epicor's announcement of its cloud-only roadmap, January 2026, as reported by CIO.com and Enterprise Times. Check the dates for your release with Epicor.

[ We help you migrate ]

Moving off Epicor on premises? We help you do it.

Tell us what you run today and where you are moving. We help you plan the move, map and check the data, load it and run both systems side by side until you switch, working with your team or your implementation partner.

[ 01 / What agents can do ]

What your agent can do in Epicor Kinetic. Every tool is one you allow or leave out.

The Epicor tools in engini, grouped by what they change. In an ERP a write is a financial event, so write tools go only to the agents that need them.

Read

Get Customers, Get Parts, Get Suppliers

Read master data with the fields you choose.

Read
Get Sales Orders, Get Jobs, Get Purchase Orders

Read orders and production, with status.

Read
Get AR Invoices, Get Part On Hand

Read what was billed and what is in stock.

Read
Run BAQ

Run any Business Activity Query your team built.

Read

Write

Create Sales Order, Update Sales Order

Enter and change orders with their lines.

Write
Create Purchase Order

Raise an order to a supplier.

Write
Create or Update Customer, Create or Update Part

Keep master data current.

Write
Call Epicor Function

Run an Epicor Function your team published, with its inputs.

Write

Delete

Delete Record

Remove a record that has not been processed.

Delete

Any endpoint

Send API Request

Call any Epicor REST service, with the sign-in added for you.

Any call

Triggers

Record Sent from Epicor

A BPM directive or Epicor Function sends a record to engini as it changes.

Event
Check for New Sales Orders, Check for New Jobs

Orders and jobs created.

Scheduled

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.

[ 02 / Connect your agent ]

Connect your AI agent to Epicor Kinetic. Four ways in, one set of permissions.

MCP

Claude, ChatGPT, Cursor

Create an MCP server in engini with your Epicor Kinetic 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 Epicor Kinetic 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 Epicor Kinetic 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 Epicor Kinetic 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 Epicor Kinetic 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 Epicor Kinetic through engini
// .cursor/mcp.json: Cursor, connected to Epicor Kinetic through engini
{
"mcpServers": {
"engini-epicor": {
"url": "<your engini MCP server address>"
}
}
}

Create the MCP server in engini with your Epicor Kinetic 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 sales orders for Acme ship this week?”
“How many of part 1010-A are on hand?”
“Enter a sales order for 25 of part 1010-A for customer ACME.”
“What jobs are late on the shop floor?”
“Run the Open Orders by Customer BAQ.”
“Which purchase orders from supplier 2001 are not received?”

Each request runs through the Epicor Kinetic 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 Epicor Kinetic. Agents and workflows, across systems.

Order to cash

Orders from every channel into Epicor

Orders from Salesforce, Shopify or a customer email become Epicor sales orders, and the customer gets the order number back.

SalesforceShopifyEpicor Kinetic
Production

Jobs people can see

When a job is late, the planner gets a Teams message with the order and the customer.

Epicor KineticMicrosoft Teams
Accounts payable

Supplier invoices matched

A supplier invoice from the inbox is read by an agent and matched to the Epicor purchase order and receipt.

OutlookEpicor Kinetic
Sales

Stock and status on request

An agent in Slack answers availability, order status and ship dates from Epicor. Its toolset holds read tools only.

SlackEpicor Kinetic

Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between Epicor Kinetic and another system engini connects is available.

[ 04 / Agent Policy ]

You decide what each agent may do in Epicor Kinetic. engini enforces it on every call.

Toolsets

Only the tools you allow

A toolset lists the Epicor Kinetic 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 Epicor Kinetic account and engini acts as that person, with their Epicor Kinetic 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 →
[ Behind your firewall ]

Epicor Kinetic behind your firewall.

If Epicor Kinetic 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 Epicor Kinetic 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 →
[ 05 / Set up ]

Connect Epicor Kinetic in three steps. Then decide what each agent may do.

Step 01

Sign in to Epicor Kinetic

In Epicor, create an API key and a user with only the security the workflows need, then add an Epicor connection with your server address, company, the user and the key, through the On-Prem Agent if Epicor runs inside your network.

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 Epicor Kinetic from Claude, ChatGPT, Cursor or your own code.

[ 06 / Questions ]

Epicor Kinetic and engini. Straight answers.

Can an AI agent write to Epicor Kinetic, or only read?

Both. engini has tools to enter and change sales and purchase orders, create and update customers and parts, call Epicor Functions and delete records. 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.

Can it use our BAQs and Epicor Functions?

Yes. Run BAQ runs any Business Activity Query, and Call Epicor Function runs any function your team published.

Does the agent act as me in Epicor Kinetic?

It acts as the Epicor user behind the connection, with that user's security. Every run is recorded under the person who started it.

Can a change in Epicor Kinetic start work?

Yes. A BPM directive or Epicor Function can send a record to engini as it changes, and scheduled triggers check for new sales orders and jobs. A workflow can include an AI agent step.

What if the tool I need is not listed?

Use Send API Request to call any Epicor Kinetic API endpoint through the same connection, and give it only to the agents that need it.