Connect Acumatica to Claude Code

Have Claude draft orders, enter bills, and update records in Acumatica. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Acumatica to Claude Code?

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

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

Full read-write Acumatica access lets Claude create and update the records you work in: draft a sales order from an email, enter an AP bill against the right vendor and account, raise a customer invoice, or update a customer, item, or inventory record, then route it for your approval. The data entry that used to mean clicking through screens happens where the records already live.

Draft a sales order from an email or quote you paste in
Create an AP bill against the right vendor, account, and project
Draft a customer invoice with line items and route it for your approval
Create or update customer, vendor, and stock item records
Post a journal entry to the correct accounts and financial period
Look up open orders or unpaid bills with a generic inquiry 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 Acumatica 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 Acumatica API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Acumatica 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 Acumatica 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 Acumatica 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 Acumatica 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 Acumatica'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 Acumatica?

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

More on the Acumatica connector

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