Connect Infor to Claude Code

Have Claude create purchase orders and update records in Infor. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Infor to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Infor, you add a Infor MCP server: a small hosted service that exposes Infor'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 Infor account. No API keys pasted into config files.

claude mcp add --transport http infor 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 Infor once connected?

Full read-write Infor access lets Claude create a purchase order, update a sales order, adjust an item or customer record, or check stock and propose a movement, then commit once you approve. The lookups and data entry that used to mean clicking through screens across CloudSuite modules happen in one place, with an approval step before anything is written.

Create or update a purchase order against the right supplier and warehouse
Draft or change a sales order and confirm pricing and delivery dates
Create or update customer, supplier, and item master records
Adjust inventory quantities or propose a stock movement after you review it
Update fields on an existing record in CloudSuite, M3, LN, or SX.e
Look up open orders matching a query and propose batched edits

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 Infor 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 Infor API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Infor 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 Infor 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 Infor 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 Infor 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 Infor'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 Infor?

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 Infor account it signs in with. Revoking access is one click in Infor.

More on the Infor connector

Infor connector for claude.ai Dynamics 365 Business Central + Claude Code Acumatica + Claude Code Epicor + 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