AI AGENTS FOR ERP
AI agents for
your ERP.
Let AI agents like Claude Code, Cursor, Windsurf, and OpenClaw query orders, check inventory, confirm shipments, and automate workflows in your Fulfil ERP.
Request a Demo
What AI agents can do
with your ERP.
Ask a question in plain English. The AI agent finds the answer in your Fulfil data, takes action, or both.
Look up orders and customers
"What's the status of order SO-12345?" — the agent checks your ERP and gives you the answer in seconds.
Check inventory levels
"How much of SKU-ABC do we have across all warehouses?" — get stock levels and forecast quantities instantly.
Confirm and process orders
"Confirm all draft orders from today" — the agent finds the orders, confirms them, and reports back what it did.
Track shipments
"Show me all shipments waiting to be processed" — see what needs attention without logging into Fulfil.
Pull reports and metrics
"What were our top 10 products by revenue last week?" — get data-driven answers from your ERP without building a report.
Automate multi-step workflows
"Find overdue invoices over $5,000 and show me the customer contacts" — the agent chains multiple queries together automatically.
HOW IT WORKS
You ask a question.
The agent does the rest.
The Fulfil CLI is a small tool that connects AI agents to your ERP data. Your developer installs it once, and from that point on, any AI agent can look up orders, check stock, confirm shipments, and more — all from a simple question.
- Set up in minutes — one install command, two environment variables, done
- Secure by default — uses your existing API permissions, all actions are logged
- Reliable results — built specifically for AI agents with structured data output
- Read-only or full access — control what the agent can do with your API key permissions
You ask a question
"How many orders are waiting to ship?"
The agent queries your ERP
It uses the Fulfil CLI to pull the data it needs from your live ERP system.
You get a clear answer
"There are 47 shipments waiting to be processed — 32 from the NYC warehouse and 15 from LA."
CLAUDE CODE ERP INTEGRATION
Claude Code
ERP integration.
Claude Code is Anthropic's CLI-based coding agent. It executes shell commands directly, making the Fulfil CLI a natural fit for Claude Code ERP integration. Connect Claude Code to your Fulfil instance in four steps.
Install the CLI
uv tool install fulfil-cli
Set environment variables
Add to your shell profile or project .env file:
Add context with CLAUDE.md
Create a CLAUDE.md in your project root to give Claude Code context about the Fulfil CLI and common commands.
Start using it
Ask Claude Code questions like "How many draft sales orders do we have?" or "Find all customer shipments waiting to be processed."
ERP integration for
every AI agent.
Any AI agent that can execute shell commands can use the Fulfil CLI for ERP access.
Cursor ERP Integration
Cursor ERP integration works through Cursor's built-in terminal. Install the Fulfil CLI, set your environment variables, and add Fulfil context to .cursorrules. Cursor can then query orders, check inventory, and manage records directly from your editor.
Windsurf ERP Integration
Windsurf ERP integration follows the same pattern. Install the CLI, set environment variables, and add context to .windsurfrules. Windsurf gets the same full ERP access as any other AI agent.
OpenClaw ERP Integration
OpenClaw ERP integration turns your messaging platforms into ERP interfaces. OpenClaw is an open-source, self-hosted AI assistant that connects to LLMs. Because it can execute shell commands, it can use the Fulfil CLI to answer business questions over WhatsApp, Slack, or Teams.
See it
in action.
Real conversations between teams and their AI agents. Whether you use Claude Code, Cursor, or OpenClaw for ERP access, the experience is the same.
Order lookup
"What's the status of order SO-12345?"
SO-12345 is confirmed, placed on March 18 for $1,250.00. The shipment has been created and is waiting to be processed.
Inventory check
"How much of SKU-ABC do we have?"
SKU-ABC has 342 units on hand and a forecast quantity of 287 units after pending orders. You have 12 units allocated to backorders.
Bulk order processing
"Confirm all draft orders from today"
Found 3 draft orders from today (SO-101, SO-102, SO-103). All 3 have been confirmed. Total value: $4,320.00.
Shipment tracking
"Show me all shipments waiting to be processed"
There are 47 shipments in "waiting" status — 32 from the NYC warehouse and 15 from LA. The oldest has been waiting since March 15.
Best practices for
AI agents for ERP.
Always use --json
When building scripts or agent workflows, always use --json to get structured output that agents can parse reliably.
| jq '.data[] | select(.state == "confirmed")'
Handle pagination
List commands return a pagination envelope. Check has_more and use the cursor for subsequent pages.
Use workflow methods for state changes
Never update state fields directly. Use the call subcommand for workflow transitions.
Check exit codes
Use exit codes for reliable error handling in agent workflows.
| Code | Meaning |
|---|---|
| 0 | Success |
| 4 | Authentication error |
| 5 | Not found |
| 6 | Forbidden |
| 7 | Validation error |
| 8 | Rate limited |
| 9 | Server error |
CLI VS MCP
Two interfaces,
different strengths.
Fulfil provides two ways to connect AI agents to your ERP: the CLI and the MCP integration. Both access the same underlying APIs, support read and write operations, and respect the same role-based permissions.
The key difference is how they use your AI agent's context window — and that determines which is right for Claude Code ERP integration, Cursor ERP integration, or conversational tools.
The context window problem
With MCP, every tool call and its response lives inside the context window. A single query returning 50 orders with 30 fields each can consume thousands of tokens, leaving less room for reasoning and follow-up work.
How the CLI helps
With the CLI, the agent executes a shell command and only the relevant output enters the context. Pipe results through jq, write to a file, or process records in a loop without raw data accumulating in the conversation.
Use the CLI when
- Large or repeated queries - Processing hundreds of records without filling the context window
- Multi-step workflows - Confirming orders, processing shipments, then checking inventory
- Scripts and automation - Shell scripts, cron jobs, and CI/CD pipelines
Use MCP when
- Conversational exploration - Asking questions in plain English via Claude's web or desktop app
- Data warehouse access - SQL queries against BigQuery for historical data and aggregations
- Non-technical users - No terminal, no installation, no command-line knowledge required
| CLI | MCP | |
|---|---|---|
| Context window impact | Low — results processed outside context | High — full payloads in context |
| Best for | Heavy data work, batch operations, scripts | Conversational exploration, quick lookups |
| Authentication | API key (keyring or env var) | OAuth via browser |
| Data warehouse | Not yet available | SQL queries via BigQuery |
| Setup | uv tool install fulfil-cli |
Connect in Claude Settings |
Questions? Answers.
What are AI agents for ERP?
AI agents for ERP are AI coding assistants — like Claude Code, Cursor, Windsurf, and OpenClaw — that can interact with your ERP system to query data, manage records, and automate workflows. With Fulfil, these agents use the CLI to access orders, inventory, financials, and more through structured shell commands.
How does Claude Code ERP integration work?
Claude Code ERP integration uses the Fulfil CLI. Install the CLI, set your API key and workspace as environment variables, and add a CLAUDE.md file with Fulfil context. Claude Code then executes fulfil commands directly to query orders, check inventory, confirm shipments, and manage your ERP data.
How does Cursor ERP integration work?
Cursor ERP integration works through Cursor's built-in terminal. Install the Fulfil CLI, set FULFIL_API_KEY and FULFIL_WORKSPACE in your environment, and add Fulfil context to your .cursorrules file. Cursor can then run fulfil commands to access your ERP data directly from the editor.
How does OpenClaw ERP integration work?
OpenClaw ERP integration lets you access Fulfil data through messaging platforms like WhatsApp, Slack, and Teams. Install the Fulfil CLI on the machine running OpenClaw, set environment variables in its configuration, and grant permission to execute fulfil commands. OpenClaw then uses the CLI to answer business questions from any connected messaging platform.
Do I need MCP if I'm using AI agents for ERP via the CLI?
No. The CLI and MCP serve different use cases. The CLI is for AI agents that can execute shell commands (Claude Code, Cursor, OpenClaw, terminal-based agents). MCP is for Claude's web and desktop apps where shell access is not available. You can use both — they are independent interfaces.
What permissions do AI agents have when accessing ERP data?
The AI agent has the same permissions as the API key you provide. Use a dedicated API key with the minimum permissions required for the agent's tasks. All operations are logged under the API key's user for audit purposes. Consider using a read-only API key if you only want the agent to query data.
Can AI agents create or modify ERP records?
Yes. The CLI supports create, update, delete, and workflow methods like call confirm. AI agents for ERP can create orders, process shipments, post journal entries, and more — all through the Fulfil CLI.
Which AI agents support ERP integration with Fulfil?
Any AI agent that can run shell commands can use the Fulfil CLI for ERP integration — Claude Code, Cursor, Windsurf, Codex, OpenClaw, and others. Any agent that supports MCP can use the MCP integration — Claude web, Claude desktop, and other MCP-compatible tools. Claude Code supports both CLI (via Bash) and MCP (via its MCP server configuration).
Ready to use AI agents with your ERP?
See how Claude Code, Cursor, and OpenClaw ERP integration works with Fulfil
Request a Demo