AI · ERP Automation
VAEGIS ERP Connector
Connect your ERP to AI without handing over a database password
Request
Call log
- Key valid · agent: order-tracking
- Scope allowed · daily quota 1,240 / 20,000 rows
- Manifest fingerprint matched · tool enabled
- SELECT · vaegis.item_stock · firm 001 / period 01
- Read through the view · 3 rows · 84 ms
Response
MCP · JSON| warehouse_no | warehouse_name | on_hand | unit |
|---|---|---|---|
| 0 | Main | 1250 | PCS |
| 1 | Bursa Store | 340 | PCS |
| 2 | Dispatch | −12 | PCS |
On-hand stock in the base unit. Negative stock is returned as is.
VAEGIS ERP Connector is a read-only Windows application that runs on your own server and opens ERP data on SQL Server to AI agents and automations. The agent cannot write free-form SQL; it can only call tested, typed business tools over MCP. The real difference is the permission model: the final security boundary is not the application but SQL Server's own object permissions. The table discovery, query writing, permission setup and accuracy testing an integrator repeats at every customer come as a ready, versioned package.
Key features
How it works
Four stages from installation to the first tool call.
Each stage ends with a human approval or an automated check. Where we are not certain, the tool does not return data; it stops.
- A signed package installs the Windows service and a local-only admin interface
- The wizard detects the SQL Server connection and the ERP profile
- The administrator selects the company and period
- A readable, plain T-SQL setup script is generated
- Your database administrator reviews and runs it
- The service itself holds no permission to change the schema
- The manifest compares a fingerprint of expected tables, columns and types
- The golden-report test matches tool output against ERP reports
- A tool that does not match exactly stays disabled, with the reason
- A key per agent: tool scope, company and daily quota
- Audit log: key, tool, time, row count, duration
- When the fiscal period changes, tools pause and a new script awaits approval
The final security boundary is SQL Server itself.
MCP Tool Layer
The agent sees only fixed, typed tools. There is no endpoint that accepts SQL text.
Connector Service
Runs as a Windows service on your server. It enforces keys, quotas, timeouts and the audit log.
vaegis Schema
Views and inline functions in a separate schema of the ERP database. A separate user per company; SELECT permission only.
Even if the application layer is bypassed, the SQL user cannot write to the ERP or read its tables directly.
Tools
This is everything the agent can see.
Each tool has a typed input schema, a fixed business definition and an accuracy test checked against the ERP's own report.
find_customer
- query
- match: code · name · tax_no
- limit ≤ 50
Returns
Customer card by code, name or tax number: code, name, city, status.
Deliberately excluded
Balance, credit limit, contact person
get_item_stock
- item_code
- warehouse_no?
Returns
On-hand stock per item and warehouse, in the base unit.
Deliberately excluded
Reserved and available stock, cost
list_open_sales_orders
- customer_code?
- item_code?
- date_from · date_to
- limit ≤ 200
- cursor
Returns
Approved, unclosed sales order lines: order no, date, item, remaining quantity.
Deliberately excluded
Price, discount, delivery estimate
Every response carries the same envelope: firm_no, period_no, pack_version, generated_at, row_count, truncated. We do not ship a tool whose accuracy we cannot prove; that is why customer balance is not in the first release.
Limits
We also write down what we do not promise.
When evaluating a security product, knowing what it does not do matters as much as knowing what it does.
- It does not control SQL access made outside the Connector.
- It does not control where the agent sends the data it receives.
- It does not verify or correct records that are wrong in the ERP.
- The golden-report test is a sample, not proof for every record.
Who it's for
- ERP integrators and software houses
- IT teams building their own automation
- Developers building agents with n8n or an MCP client
- Companies running an ERP on SQL Server
Data security
ERP data stays on site
Only licensing and updates run in the cloud; no ERP data goes there
No password for the agent
The agent connects with a key that can be revoked in one step
Sensitive fields are never selected
A field outside the package cannot leave; no reliance on masking
The audit log holds no data
Who, which tool, when, how many rows; no ERP data or credentials
The product is in development. If you build automation on a SQL Server-based ERP, we would like to hear what you need.
Request a callProducts
Software we build ourselves.
Let's design your project together.
In a 30-minute discovery call we listen to your processes and systems, and tell you plainly which AI solution will actually work and how long the first prototype will take.