< Back to all integrations

Sage 200

ERP & Finance

Connect AI agents and workflows to Sage 200: customers, suppliers, stock, sales and purchase orders, invoices and nominal journals.

Book a demo
[ Sage 200 + engini ]

Sage 200 for AI agents and workflows.

engini lets your AI agents and workflows work in Sage 200, the business management system widely used by mid-sized companies in the UK and Ireland: read customers, suppliers and stock, enter sales orders and purchase orders, post sales and purchase invoices, enter nominal journals, read balances, and start a workflow when records change. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.

MCPPython and TypeScript SDKCLIREST APIWorkflow Studio
Sign-inOAuth 2 through Sage ID, for the company you choose
ReachCustomers, suppliers, stock items, sales and purchase orders, invoices and nominal ledger
EditionsSage 200 Standard and Professional
[ 01 / What agents can do ]

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

The Sage 200 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 Suppliers, Get Stock Items

Read master data and stock levels.

Read
Get Sales Orders, Get Purchase Orders

Read open orders.

Read
Get Sales Invoices, Get Purchase Invoices

Read billing and what is owed.

Read
Get Nominal Codes, Get Balances

Read the nominal ledger.

Read

Write

Create Sales Order, Create Purchase Order

Enter orders with their lines.

Write
Post Sales Invoice, Post Purchase Invoice

Post invoices to the ledgers.

Write
Create Nominal Journal

Post a journal.

Write
Create or Update Customer, Supplier or Stock Item

Keep master data current.

Write

Any endpoint

Send API Request

Call any Sage 200 API endpoint, with the sign-in added for you.

Any call

Triggers

Check for New or Changed Records

Orders, invoices or customers added or changed.

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

MCP

Claude, ChatGPT, Cursor

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

Create the MCP server in engini with your Sage 200 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 customers are past their payment terms?”
“How many of stock item BOLT-10 are available?”
“Enter a sales order for Acme for 500 of BOLT-10.”
“Which purchase invoices are due this week?”
“Post the month-end accrual journal.”
“What were sales by nominal code last quarter?”

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

Order to cash

Orders from the CRM and the store

Orders from Salesforce, HubSpot or Shopify become Sage 200 sales orders, and status flows back.

SalesforceHubSpotShopifySage 200
Accounts payable

Supplier invoices from the inbox

A supplier invoice from email is read by an agent and posted in Sage 200.

OutlookSage 200
Subsidiaries

UK entities that reconcile

A UK subsidiary on Sage 200 sends sales and journals to headquarters on NetSuite or SAP.

Sage 200NetSuiteSAP S/4HANA
Finance

Answers in plain words

An agent in Teams answers balances, stock and order questions. Its toolset holds read tools only.

Microsoft TeamsSage 200

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

[ 04 / Agent Policy ]

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

Toolsets

Only the tools you allow

A toolset lists the Sage 200 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 Sage 200 account and engini acts as that person, with their Sage 200 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 →
[ 05 / Set up ]

Connect Sage 200 in three steps. Then decide what each agent may do.

Step 01

Sign in to Sage 200

Add a Sage 200 connection, sign in with Sage ID and choose the company. Use a user whose role covers only what the workflows need.

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

[ 06 / Questions ]

Sage 200 and engini. Straight answers.

Can an AI agent write to Sage 200, or only read?

Both. engini has tools to enter sales and purchase orders, post invoices and nominal journals, and keep customers, suppliers and stock items 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 Sage 200?

It acts as the Sage 200 user who signed in, with that user's role. Every run is recorded under the person who started it.

Can a change in Sage 200 start work?

Yes. Scheduled triggers check Sage 200 for new or changed records. A workflow can include an AI agent step.

What if the tool I need is not listed?

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