Mapping every API endpoint to its own MCP tool burns context tokens, triggers quadratic roundtrips, and turns agents into fragile state machines. Here is how DataTether's composite tools bundle multi-entity workflows into atomic, token-efficient calls.
A sales order isn't one record. When AI creates the header but the line item fails, someone has to find and delete the orphan by hand. Atomic writes remove the entire failure class.
SAP HANA keeps your ERP data in memory and stores it in columns, which is why S/4HANA answers in seconds instead of overnight. Here's what that speed actually buys you — and how AI can tap live HANA-backed data without touching the database or losing governance.
Every generic 'connect AI to your API' demo dies on its first real SAP Gateway service. Here are the four quirks that kill it — and what handling them properly actually involves.
You don't need Joule, a migration, or a custom MCP server to point Claude, ChatGPT, Claude Code, Codex, or any MCP client at your SAP system. If your SAP exposes OData, there is a governed path that takes an afternoon.
Joule is real — for the SAP stack it was built for. If you run ECC or on-premise S/4HANA, or your company standardised on Claude or ChatGPT, here is where the gap is and what your options are.
A new layer is forming between enterprise systems and AI assistants: platforms that turn OData services into governed MCP tools. What that means, why it exists, and what to look for in one.
'No code' usually sells toy automation. For SAP, it has to mean something more specific: no ABAP changes, no middleware to host, no MCP server to write — and governance that survives an audit.
All-or-nothing access is why AI-to-ERP projects either stall in read-only purgatory or terrify compliance. The working model splits the problem: reads flow freely, writes wait for a named human.
You don't need a sandbox SAP system to judge the OData-to-MCP idea. A public demo service and one guided flow take you from a URL to an AI answering real queries — here's the walkthrough.
Two board-level pressures — the ECC maintenance deadline and the AI mandate — are usually treated as one sequenced project: migrate first, AI after. That sequencing quietly costs years.