01. Connect Epicor
An administrator installs the Cutova solution and registers your Epicor instance. On-premise setups can use the outbound gateway.
How it works
Connect Epicor. Choose a job. Get moving.
Your administrator sets up the connection and tools. Your team uses a compatible assistant to ask questions and do the work.
Two roles in setup.
02. Choose the work
Publish the tools you want to use, or install a Skill Pack and its Epicor prerequisites.
03. Connect and ask
Each person connects a compatible assistant and authorizes access. Ask a question, review the result, and build from there.
For example, publish a sales BAQ your team already uses. The assistant can call it to answer a sales question from live results.
A Skill Pack bundles tools and guidance for a specific job. Installing a pack may also require Epicor Functions, BAQs or other prerequisites.
Read data. Build things. Run approved workflows.
Your Epicor tools
Publish the BAQs, Business Objects and Functions you want available. Review the tools included in a pack before enabling them.
Live data for the answer
Tool calls retrieve data from your Epicor instance. Review the query and the assistant’s conclusions before acting.
Work through Epicor APIs
Writes use the configured APIs and applicable server-side validation and BPMs. Screen-only logic and manual interaction steps are not necessarily reproduced.
Help with your backlog
Build BAQs, create and edit Epicor Functions, or create and update Kinetic dashboards and customizations. Executive Insights helps answer business questions. Review and test the generated work in your sandbox.
No pack for your job? Make it your own.
The packs are starting points. Your published tools determine what else your assistant can work with.
Equip it
Publish a BAQ, Business Object or Epicor Function as a tool. Give it a clear description so your assistant knows when to use it.
Give it the steps
Combine tools with instructions for your workflow. You or your team can build a pack around a job you repeat.
Build on what works
Test with your Epicor instance, then add tools as your needs grow. Your plan sets the number of enabled tools. New business logic may need development.
The Epicor Functions pack helps create and edit Functions. Publishing one as an assistant tool is a separate choice.
Your sign-in and the service connection.
End users sign in with Epicor. Cutova does not receive their Epicor passwords during that sign-in.
Cutova stores the service account username, password and API key configured by your administrator, encrypted with AES-256-GCM. Tool calls use this connection with the signed-in user's identity through Epicor impersonation.
Tool results pass through Cutova to your chosen AI client and provider. The optional AI schema-description helper sends schema metadata to its configured provider when enabled. Read the data-handling details.
Model Context Protocol
The open standard for connecting AI clients to tools and data. Cutova is an MCP server: no Cutova plugin, no Cutova SDK, nothing built per client.
Remote, over Streamable HTTP
Connect a compatible assistant to the remote server URL. Administrators install the Epicor solution first; an on-premise connection can also require the gateway.
OAuth 2.1 with PKCE, and dynamic client registration
A client registers itself and sends you to your own Epicor to sign in. No API key to paste into a chat window.
Two protocol versions at once
Cutova supports two MCP protocol revisions. The client must support a compatible revision and the authentication and features your workflow needs.
Client authentication, Skills, file handling and interactive MCP Apps vary. Check your client's setup guide.
Review the work before you rely on it.
Choose a focused starting point
Start with a read-only query or a sandbox workflow. Check which records and operations each enabled tool can access.
Check approval settings
Use your AI client’s approval settings to review tool calls before they run. Start with a focused workflow and expand once you have checked the results.
Check the result in Epicor
Review query filters, totals and generated changes. Confirm the relevant Epicor permissions and server-side rules for the workflow you intend to use.