< Back to all integrations

SYSPRO

ERP & Finance

Connect AI agents and workflows to SYSPRO: customers, stock, sales orders, purchase orders, jobs and any e.net business object, with triggers on changes.

Book a demo
[ SYSPRO + engini ]

SYSPRO for AI agents and workflows.

engini lets your AI agents and workflows work in SYSPRO: query customers, stock, sales orders and jobs, enter sales and purchase orders, add customers and stock codes, run any e.net business object, and start a workflow when SYSPRO sends a record. Manufacturers and distributors keep SYSPRO and the systems around it in step. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.

MCPPython and TypeScript SDKCLIREST APIWorkflow Studio
Sign-inA SYSPRO operator for e.net Solutions, for the company you choose
ReachCustomers, stock, sales orders, purchase orders, jobs and every e.net business object
DeploymentSYSPRO cloud, or on premises through the On-Prem Agent
[ 01 / What agents can do ]

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

The SYSPRO 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 Customer, Get Customers

Read customers, balances and terms.

Read
Get Stock Item, Get Stock Availability

Read stock codes and what is available by warehouse.

Read
Get Sales Order, Get Sales Orders

Read orders and their status.

Read
Get Jobs, Get Purchase Orders

Read production and purchasing.

Read

Write

Create Sales Order

Enter an order with its lines.

Write
Create Purchase Order

Raise an order to a supplier.

Write
Create or Update Customer, Create or Update Stock Item

Keep master data current.

Write
Run Business Object

Run any e.net query, setup or transaction business object you allow.

Write

Triggers

Record Sent from SYSPRO

A SYSPRO trigger or business activity sends a record to engini as it changes.

Event
Check for New Sales Orders

Orders entered.

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 SYSPRO. Four ways in, one set of permissions.

MCP

Claude, ChatGPT, Cursor

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

Create the MCP server in engini with your SYSPRO 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 are on back order?”
“How many of stock code A100 are available in warehouse FG?”
“Enter a sales order for 50 of A100 for customer 0000001.”
“Which jobs are behind schedule?”
“Which purchase orders from supplier 0000002 are not received?”
“Add this customer from the new account form.”

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

Order to cash

Orders from every channel into SYSPRO

Orders from Shopify, Salesforce or EDI become SYSPRO sales orders, and the confirmation goes back.

ShopifySalesforceEDI (X12, EDIFACT, AS2)SYSPRO
Production

Late jobs, flagged

When a job falls behind, the planner gets a Teams message with the order and the customer.

SYSPROMicrosoft Teams
Finance

SYSPRO in the warehouse

Orders, stock and ledger data land in Power BI or Snowflake on a schedule.

SYSPROPower BISnowflake
Sales

Stock and status on request

An agent in Slack answers availability and order status from SYSPRO. Its toolset holds read tools only.

SlackSYSPRO

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

[ 04 / Agent Policy ]

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

Toolsets

Only the tools you allow

A toolset lists the SYSPRO 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 SYSPRO account and engini acts as that person, with their SYSPRO 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 ]

SYSPRO behind your firewall.

If SYSPRO 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 SYSPRO 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 SYSPRO in three steps. Then decide what each agent may do.

Step 01

Sign in to SYSPRO

Create a SYSPRO operator for e.net Solutions with access only to the business objects the workflows need, then add a SYSPRO connection with your server, company and that operator, through the On-Prem Agent if SYSPRO 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 SYSPRO from Claude, ChatGPT, Cursor or your own code.

[ 06 / Questions ]

SYSPRO and engini. Straight answers.

Can an AI agent write to SYSPRO, or only read?

Both. engini has tools to enter sales and purchase orders, create and update customers and stock items, and run e.net business objects. 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.

What if the tool I need is not listed?

Run Business Object runs any e.net query, setup or transaction business object, so anything SYSPRO exposes through e.net is in reach. Give it only to the agents that need it.

Does the agent act as me in SYSPRO?

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

Can a change in SYSPRO start work?

Yes. A SYSPRO trigger or business activity can send a record to engini as it changes, and a scheduled trigger checks for new sales orders. A workflow can include an AI agent step.