01
MCP tools
Let agents search products, inspect definitions, open revisions, and request permitted product operations.
Resource · MCP & integrations
Expose reviewed product intelligence without exposing the database.
ConfigAI is designed to become a product-data and product-tool layer for configurators, agents, CAD/modeling workers, and business systems. Integrations should consume versioned contracts and scoped tools rather than bypassing domain rules.
02
Supplier adapters
pCon Catalog, pCon / OFML, Gatekeeper-authorised sources, and later ERP/PIM adapters preserve provider boundaries.
03
Modeling workers
Blender, build123d, and specialized 3D services operate through project tickets and artifact contracts.
MCP surface
Agents need product capabilities, not raw table access.
The MCP layer should publish stable operations around the product domain: search, read exact revisions, inspect options/relationships, start bounded workflows, and submit proposals.
Catalog search
Find products, families, source identities, and relevant assets under workspace scope.
Property introspection
Read Product Type fields, allowed values, current profile revision, and configuration constraints.
Configuration tools
Evaluate permitted configuration/rule operations against exact product revisions.
3D project tools
Create modeling projects, add sources, request revisions, and read approved artifacts through the Studio contract.
Import tools
Start bounded research/import work and submit evidence-backed proposals instead of writing products directly.
Review-aware mutations
Actions that change active product truth return proposals or require reviewer-authorized Apply.
External systems
Source adapters and consumers are both integrations, but with different authority.
A supplier integration can be authoritative for source facts without becoming authoritative for the final ConfigAI product. A downstream configurator can consume reviewed ConfigAI data without being allowed to mutate its semantics.
Source
pCon / OFML
Source-side provider and configuration data with preserved provider identities and optional private access.
Source
Web / PDF
Human-facing source evidence interpreted through the import pipeline.
Consumer
Configurator / CPQ UI
Consumes reviewed Product Types, product profiles, rules, configurations, and assets.
Roadmap
ERP / SAP / production
Future consumers/producers for commercial and manufacturing outputs after the base product contract is stable.
3D tool ecosystem
Keep specialized modeling technology replaceable.
Image-to-3D, Blender, build123d, semantic segmentation, PBR generation, and future USD tooling can evolve quickly. The stable boundary should be the Studio project, evidence, checkpoint, review, and product-attach contract.
Studio project
Owns product/source context, user intent, runtime profile, and revision lifecycle.
Tool router
Selects the appropriate deterministic or generative worker for the requested modeling operation.
Evolving
Worker
Runs Blender, build123d, reconstruction, segmentation, material, or validation jobs under bounded inputs.
Reviewed artifact
Only approved outputs become durable product assets.
ConfigAI
A product API designed for agents and applications at the same time.
Reviewed product semantics stay behind the service boundary while MCP, UI, supplier adapters, and modeling workers receive exactly the capabilities they need.