Business data, available to AI. Under control.
The service through which THUX CODE connects ERP, CRM and business system databases to AI agents, with rules set by the customer. The connection uses the Model Context Protocol (MCP), the open standard that lets an artificial intelligence assistant access external data sources.
ERP, CRM and business systems hold the data that matters, but they rarely offer APIs and can almost never be modified. THUX CODE installs an MCP connector that works directly on the live database, translates the technical schema into business terms and exposes only the agreed operations. The same access is available to the VERIAX framework and to assistants that support MCP, such as Claude, ChatGPT and Microsoft Copilot.
What's included
Analysis of the database and selection, together with the customer, of the tables, fields and operations to expose.
Translation of technical names into business terms, understandable for the agent and for the reader.
Analyses declared in configuration: revenue by customer, monthly trends, rankings. They are computed by the database, not by the agent: the numbers are the business system's, not a model's estimate.
Controlled writing, on request: only the agreed operations are enabled, such as recording an order or updating the status of a case, with rules and fields set by the customer.
Administration panel to decide what to expose, with drafts, publishing and change history.
Access via MCP for AI agents and via REST API for other systems, with CSV and Excel export on request.
Works on SQL Server and PostgreSQL, with the test suite run on both at every release. MySQL and MariaDB are planned, not yet in the test matrix.
Installation within the customer's perimeter, with a dedicated instance and its own credentials.
How it works
- 1
THUX CODE analyzes the database with the business system's owner and defines what to expose for reading and what for writing. This phase needs only the database schema: data never leaves the customer's perimeter at any stage.
- 2
THUX CODE configures functions and perimeters and verifies the results against the business system. An inconsistent declaration stops the service from starting: nothing is published that has not been verified.
- 3
THUX CODE installs the service in production within the customer's perimeter, with each department's access keys, and connects it to VERIAX or to the chosen AI assistant.
- 4
To expose new data, the connector's configuration is changed, not the business system: no intervention on the customer's database.
Benefits
- No changes to the business system: no views, procedures or indexes, in compliance with maintenance contracts. Where an exposure would require a missing index, the service declares it at startup instead of silently degrading.
- By default the service is read-only: the agent uses declared functions and does not write queries.
- Writing is enabled operation by operation, only where the customer authorizes it, with a separate SQL user that cannot delete rows or modify the schema. It is logged like every other call.
- Exact, verifiable numbers: totals and rankings are computed by the database, the AI presents them.
- The production database stays protected: a separate read-only SQL user, limits on the number of rows returned, execution timeouts, call rate limiting, temporary caching of results and an emergency switch that shuts everything down.
- Each department sees only its own perimeter, with separate access keys that expire and can be revoked one by one.
- Every call is logged: function requested, caller, rows returned and timings.