Connect Epicor to Claude Code

Make Claude create orders and update records in Epicor. From the terminal, inside the sessions where you already work.

How do you connect Epicor to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Epicor, you add a Epicor MCP server: a small hosted service that exposes Epicor's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Epicor account. No API keys pasted into config files.

claude mcp add --transport http epicor https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Epicor once connected?

Full read-write Epicor access lets Claude create and update sales orders, adjust inventory, post or release records, and update customer details once you approve. The lookups and data entry that meant switching between Epicor screens and a chat window happen in one place, with the same permissions your account already carries.

Create a sales order from a customer request and add line items
Update inventory quantities or post a stock adjustment
Create or update a customer or supplier record
Release a job or work order after you confirm the details
Update the status of a purchase order or quote
Look up part availability across sites and propose a reorder

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Epicor access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Epicor API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Epicor changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Epicor connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Epicor connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Epicor account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Epicor's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Epicor?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Epicor account it signs in with. Revoking access is one click in Epicor.

More on the Epicor connector

Epicor connector for claude.ai Dynamics 365 Business Central + Claude Code Acumatica + Claude Code Infor + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us