This page documents product direction, not released compatibility. Any integration must be implemented, validated, and documented before it is presented as available.
Adapter boundary
A Model Context Protocol integration should connect through a replaceable adapter rather than becoming a hidden dependency of the Colvri core.
Requirements made visible
The integration should state its source, runtime, storage, hardware fit, and license terms before installation.
Availability stays honest
Until an adapter passes implementation and validation, Colvri describes it as planned support rather than a working feature.