< Back to all integrations

JobBOSS2 and M1 (ECi)

ERP & Finance

Connect AI agents and workflows to ECi JobBOSS² and M1: quotes, jobs, customers, parts, purchase orders, shipments and invoices for job shops.

Book a demo
[ JobBOSS² and M1 (ECi) + engini ]

JobBOSS² and M1 (ECi) for AI agents and workflows.

engini lets your AI agents and workflows work in JobBOSS² and M1 from ECi, the ERPs for job shops and make-to-order manufacturers: read quotes, jobs and their routings, customers, parts and inventory, read purchase orders, shipments and invoices, enter orders and customers, 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-inA JobBOSS² or M1 user, and read access to its SQL Server database
ReachQuotes, jobs, routings, customers, parts, inventory, purchase orders, shipments and invoices
DeploymentECi cloud, or on premises through the On-Prem Agent
[ 01 / What agents can do ]

What your agent can do in JobBOSS² and M1 (ECi). Every tool is one you allow or leave out.

The JobBOSS² and M1 (ECi) 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

Get Quotes, Get Jobs

Read quotes and jobs with their routing and status.

Read
Get Customers, Get Parts, Get Inventory

Read master data and stock.

Read
Get Purchase Orders, Get Shipments, Get Invoices

Read purchasing, shipping and billing.

Read
Run Query

Read any table with a SQL query. Read only.

Read

Write

Create Order

Enter a customer order.

Write
Create or Update Customer, Create or Update Part

Keep master data current.

Write

Triggers

Check for New or Changed Records

Quotes, jobs, shipments or invoices 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 JobBOSS² and M1 (ECi). Four ways in, one set of permissions.

MCP

Claude, ChatGPT, Cursor

Create an MCP server in engini with your JobBOSS² and M1 (ECi) 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 JobBOSS² and M1 (ECi) 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 JobBOSS² and M1 (ECi) 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 JobBOSS² and M1 (ECi) 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 JobBOSS² and M1 (ECi) 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 JobBOSS² and M1 (ECi) through engini
// .cursor/mcp.json: Cursor, connected to JobBOSS² and M1 (ECi) through engini
{
"mcpServers": {
"engini-jobboss-m1": {
"url": "<your engini MCP server address>"
}
}
}

Create the MCP server in engini with your JobBOSS² and M1 (ECi) 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 jobs for Acme are behind schedule?”
“Which quotes from last month have not turned into orders?”
“How many of part 4410-A are on hand?”
“Enter an order for 250 of part 4410-A for Acme.”
“What did we ship this week?”
“Which purchase orders for material are late?”

Each request runs through the JobBOSS² and M1 (ECi) 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 JobBOSS² and M1 (ECi). Agents and workflows, across systems.

Sales

Quotes and orders from the CRM

A deal won in HubSpot or Salesforce becomes a JobBOSS² or M1 order, and job status flows back to the account.

HubSpotSalesforceJobBOSS² and M1 (ECi)
Finance

Invoices in the books

Invoices reach QuickBooks when finance runs there.

JobBOSS² and M1 (ECi)QuickBooks
Production

Late jobs, flagged early

When a job falls behind, the planner and the customer rep hear in Teams.

JobBOSS² and M1 (ECi)Microsoft Teams
Customer service

Order status without walking the floor

An agent answers where a job is and when it ships. Its toolset holds read tools only.

SlackJobBOSS² and M1 (ECi)

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

[ 04 / Agent Policy ]

You decide what each agent may do in JobBOSS² and M1 (ECi). engini enforces it on every call.

Toolsets

Only the tools you allow

A toolset lists the JobBOSS² and M1 (ECi) 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 JobBOSS² and M1 (ECi) account and engini acts as that person, with their JobBOSS² and M1 (ECi) 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 ]

JobBOSS² and M1 behind your firewall.

If JobBOSS² and M1 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 JobBOSS² and M1 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 JobBOSS² and M1 (ECi) in three steps. Then decide what each agent may do.

Step 01

Sign in to JobBOSS² and M1 (ECi)

Install the engini On-Prem Agent on a server that can reach the JobBOSS² or M1 database, create a read-only SQL login and an application user for writes, then add the connection.

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 JobBOSS² and M1 (ECi) from Claude, ChatGPT, Cursor or your own code.

[ 06 / Questions ]

JobBOSS² and M1 (ECi) and engini. Straight answers.

Can an AI agent write to JobBOSS² and M1 (ECi), or only read?

Both. engini has tools to enter orders and keep customers and parts 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 it work with both JobBOSS² and M1?

Yes. Each is its own connection, with the same kinds of tools.

What if the tool I need is not listed?

Run Query reads any 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 JobBOSS² and M1 (ECi)?

It reads as the SQL login and writes as the application user behind the connection. Every run is recorded under the person who started it.

Can a change in JobBOSS² and M1 (ECi) start work?

Yes. Scheduled triggers check for new or changed quotes, jobs, shipments and invoices. A workflow can include an AI agent step.