Global Shop Solutions
Connect AI agents and workflows to Global Shop Solutions: customers, parts, quotes, sales orders, work orders, inventory, purchase orders and invoices.
Book a demoGlobal Shop Solutions for AI agents and workflows.
engini lets your AI agents and workflows work in Global Shop Solutions, the ERP for job shops and make-to-order manufacturers: read customers, parts and inventory, read quotes, sales orders and work orders with their status on the floor, enter sales and purchase orders, read invoices, and start a workflow when records change. The shop floor and the office see the same orders. 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 Global Shop Solutions. Every tool is one you allow or leave out.
The Global Shop Solutions tools in engini, grouped by what they change. Write tools go only to the agents that need them.
Read
Read master data.
Read quotes and orders with their status.
Read jobs, routings and where each one is on the floor.
Read stock, purchasing and billing.
Read any Global Shop table with a SQL query. Read only.
Write
Enter an order with its lines.
Raise an order to a vendor.
Keep master data current.
Triggers
Orders, work orders or invoices added or changed.
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 Global Shop Solutions. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your Global Shop Solutions 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 Global Shop Solutions 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 Global Shop Solutions 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 Global Shop Solutions 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 Global Shop Solutions through engini
{
"mcpServers": {
"engini-global-shop-solutions": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your Global Shop Solutions 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 Global Shop Solutions tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build on Global Shop Solutions. Agents and workflows, across systems.
Quotes and orders from the CRM
A deal won in HubSpot or Salesforce becomes a Global Shop sales order, and job status flows back to the account.
Late jobs, flagged early
When a work order falls behind, the planner and the customer rep hear in Teams.
Invoices in the books
Invoices from Global Shop reach QuickBooks or NetSuite when finance runs elsewhere.
Order status without a call to the floor
An agent answers where an order is and when it ships. 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 Global Shop Solutions and another system engini connects is available.
You decide what each agent may do in Global Shop Solutions. engini enforces it on every call.
Only the tools you allow
A toolset lists the Global Shop Solutions 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 Global Shop Solutions account and engini acts as that person, with their Global Shop Solutions 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.
Global Shop Solutions behind your firewall.
If Global Shop Solutions 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 Global Shop Solutions 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 Global Shop Solutions in three steps. Then decide what each agent may do.
Sign in to Global Shop Solutions
Install the engini On-Prem Agent on a server that can reach Global Shop, create a user with access only to what the workflows need, then add a Global Shop connection with your server and that user.
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 Global Shop Solutions from Claude, ChatGPT, Cursor or your own code.
Global Shop Solutions and engini. Straight answers.
Can an AI agent write to Global Shop Solutions, or only read?
Both. engini has tools to enter sales and purchase orders and to create and update customers and parts. 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 Query reads any Global Shop table, and new tools can be added for the areas you use. Talk to us about what you need.
Does the agent act as me in Global Shop Solutions?
It acts as the Global Shop user behind the connection. Every run is recorded under the person who started it.
Can a change in Global Shop Solutions start work?
Yes. Scheduled triggers check Global Shop for new or changed orders, work orders and invoices. A workflow can include an AI agent step.