Business integrations: Odoo, 1C, BAS and BAF

Tvijo Business Integrations is a proposed family of MCP packages for connecting AI assistants to business systems. We are starting with an experimental Odoo read-only pilot. Use this page to choose a scenario and understand what has been tested before requesting an implementation.

Status updated 29 October 2026. This catalogue describes an offer under validation; it is not a list of integrations already included in the released TvijoCode editor.

Choose your business system

We add a system when there is a repeatable customer problem and a verified integration path. An MCP listing alone does not demonstrate either.

Choose your role and outcome

• ERP integrator: qualify API access and data quality before committing to a larger project.
• Sales or operations manager: obtain a bounded answer with its period, currency, company and source records.
• Warehouse or purchasing team: compare physical stock with reservations without changing orders.
• Analyst: define a reproducible data extract before commissioning a DWH or forecasting project.
• ERP developer: review a supplied module diff and define the tests needed for the change.

These are pilot use cases, not independently measured customer outcomes. We do not claim a percentage reduction in implementation time.

What MCP contributes

MCP gives a client a standard way to discover and call tools. Our business adapter determines the permitted systems, fields and operations. The ERP still enforces its own access rules. The host and chosen model determine where returned data is processed.

The planned path is: TvijoCode / VS Code host → scoped MCP adapter → ERP API → source-linked result. Compatibility of the server with an SDK is tested separately from compatibility with a released editor or the DSHREM agent.

Start with one verifiable task

1. Read the Odoo pilot guide and its limitations.
2. Try a synthetic demonstration with fabricated data; no production credentials are needed.
3. Agree on one scenario, a data owner, the comparison report and an acceptance criterion.
4. Check the actual ERP version, API entitlement, permissions and permitted model provider.
5. Run a scoped pilot. Only then discuss recurring operation, support and a wider deployment.

The proposed commercial sequence is a scoped diagnostic, a fixed-scope pilot, then support if the customer uses the result repeatedly. Scope and price are quoted in writing. This page takes no payment and grants no access to your systems.

Request an Odoo pilot

Open an Odoo pilot enquiry on GitHub. A GitHub account is required. Issues in this repository are public: provide only your role, ERP version, hosting type and a general description of the problem. Never include keys, personal records, private URLs or customer exports.

For sensitive requirements, request a private intake channel without posting the sensitive details. Submitting an enquiry is not acceptance into a pilot or a promise of a response time.

Public presentation and private implementation

The public documentation repository contains the product explanation and examples. The Odoo prototype implementation is kept in a separate private repository. Client data belongs in neither repository. Access to source and commercial distribution require agreed terms.

Hotido research and FineDG analytics have different users and access boundaries. This ERP pilot does not automatically connect either service to your records or to financial execution.

Evidence and reading

• Odoo read-only pilot: supported scope, example and pending checks.
• Existing Tvijo MCP review: a separate tool for a supplied diff.
• Permissions and data.
• Official MCP documentation.

This page is an automated editorial publication. It does not claim a human security review, a customer case study, accounting compliance or completed production deployment.