Before you start

These requirements are for the administrator setting up an Epicor environment. If your organization already uses Cutova, ask for its MCP URL and connect your AI client.

On the Epicor side

Cutova supports Epicor Kinetic 2025.2 and newer out of the box. Complete the connection and solution setup below. AI client capabilities can vary by client and version.

You need	Why
The Epicor application server URL	Cutova calls this. Example: https://erp.example.com/EpicorLive
Rights to install a solution	The console gives you a .cab to install in Epicor
A service account with API access	Every Epicor call travels on it, with the signed-in person applied on top as impersonation
An Epicor API key	Required when you add the instance. It can be scope-restricted: see below.
Rights to use Solution Workbench	You install the Cutova solution there
The default company ID	Used when a person has not chosen one

Scoping the API key

You can restrict the Epicor API key rather than leaving it wide open. If you do, the scope has to include everything Cutova will call:

• Every BAQ you intend to publish as a tool.
• Every Epicor Function you intend to publish as a tool.
• Every Business Object service and operation you intend to expose.
• The BAQs and Functions required by any pack you install.
• The MCP Functions that arrive with the Cutova solution package.

A scope that misses one of these does not fail at setup. It fails later, when somebody calls the tool that needs it. So widen the scope at the same time you publish a new tool, not afterwards.

On the Cutova side

• A Cutova account with the Admin role. Registering an Epicor instance needs it.

On each person’s machine

• An AI client that supports remote MCP servers over Streamable HTTP.
• An Epicor login for that person. This is not optional and not shared. Each person signs in as themselves, which is what keeps their Epicor permissions intact.

Network access

The AI client connects to Cutova. Cutova must reach Epicor directly or through the gateway. For a private server, the gateway opens an outbound connection; you do not need to expose Epicor publicly for tool calls.

Each person’s browser must also reach the Epicor sign-in page during authorization. For a private Epicor server, that may require your corporate network or VPN. The gateway relays API calls; it does not make the browser sign-in page public.

Plans and usage

The pricing page lists current plans and limits. The console’s Subscription page shows your organization’s plan and usage. Check its available instance and tool capacity before adding another environment or installing a pack.

You can publish your own existing BAQs and Functions as tools. Custom BAQ or Function development and custom pack work are separately quoted services.

If Epicor is not reachable from the internet

You need the on-premise gateway, and it has to be connected before you register the instance. See When Epicor is not on the internet.

Next: Register your Epicor instance.

Plan and trial access

Choose ongoing Free or a 14-day eligible paid-plan trial during signup. No credit card is required to start a trial. Check trial and billing guidance and current prices and limits. If your organization already has an instance, use the client instructions.