~1 minIn draft
Wiring AI agents into NetSuite over MCP
What it takes to put a natural-language interface on an ERP without handing a language model the keys: tool contracts, scoped agents, and an orchestrator that knows when not to use AI.
The Model Context Protocol makes "connect an LLM to your ERP" sound like an afternoon project. The part that takes real architecture is everything around the connection: designing tool contracts an agent can't misuse, scoping each agent to one financial domain, and building an orchestrator that treats the LLM as a routing and synthesis layer — not a database client.
What this essay will cover
- Tool contracts as the guardrail: typed, scoped, enumerable
- One agent per subledger — why domain boundaries beat one mega-agent
- The orchestrator's real job: knowing when not to use the LLM
This essay is in draft. The full write-up lands here when it's ready.
MCP · NetSuite · Agents