Brightpearl
Connect AI agents and workflows to Brightpearl: products, inventory by warehouse, sales orders, purchase orders, customers, fulfillment and invoices.
Book a demo
Brightpearl for AI agents and workflows.
engini lets your AI agents and workflows work in Brightpearl, the retail operations platform from Sage for multichannel merchants: read products and inventory by warehouse, enter and update sales orders, raise purchase orders, follow goods-out notes and fulfillment, read invoices and customers, and start a workflow the moment Brightpearl reports an order or stock change. 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 Brightpearl. Every tool is one you allow or leave out.
The Brightpearl 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
Read products and stock by warehouse.
Read orders and fulfillment.
Read purchasing.
Read who bought and what was billed.
Write
Enter an order and move it through your workflow.
Raise an order to a supplier.
Keep records current.
Correct stock in a warehouse.
Any endpoint
Call any Brightpearl API endpoint, with the token added for you.
Triggers
An order arrived or moved to a new status.
Stock moved for a product.
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 Brightpearl. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your Brightpearl 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 Brightpearl 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 Brightpearl 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 Brightpearl 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 Brightpearl through engini
{
"mcpServers": {
"engini-brightpearl": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your Brightpearl 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 Brightpearl tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build on Brightpearl. Agents and workflows, across systems.
Orders from every channel
Orders from Shopify, Amazon and wholesale land in Brightpearl, and status flows back to each channel.
Order answers on the ticket
When a ticket arrives, an agent adds the Brightpearl order and shipment status to Zendesk or Gorgias.
Stock before it runs out
When products fall below reorder level, purchase orders are drafted and the buyer hears in Slack.
Retail numbers on request
An agent answers sales, margin and stock questions. Its toolset holds read tools only.
Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between Brightpearl and another system engini connects is available.
You decide what each agent may do in Brightpearl. engini enforces it on every call.
Only the tools you allow
A toolset lists the Brightpearl 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 Brightpearl account and engini acts as that person, with their Brightpearl 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.
Connect Brightpearl in three steps. Then decide what each agent may do.
Sign in to Brightpearl
In Brightpearl, create an app for engini and copy its token, then add a Brightpearl connection with your account ID and the token.
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 Brightpearl from Claude, ChatGPT, Cursor or your own code.
Brightpearl and engini. Straight answers.
Can an AI agent write to Brightpearl, or only read?
Both. engini has tools to create and update sales orders, raise purchase orders, correct stock and keep customers and products current. 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 the agent act as me in Brightpearl?
It acts as the Brightpearl app behind the connection. Every run is recorded under the person who started it.
Can a change in Brightpearl start work?
Yes. Brightpearl notifies engini when orders are created or change status and when stock moves. A trigger starts a workflow, and that workflow can include an AI agent step.
What if the tool I need is not listed?
Use Send API Request to call any Brightpearl API endpoint through the same connection, and give it only to the agents that need it.