Known issues and limitations for Content Cortex containers

The following information describes known issues and limitations when you deploy Content Cortex containers. The section covers the limitations for both the deployment process and for using the Content Cortex components in a container environment.

Support details for Content Cortex components in container environments

For details about support in container environments, see the Software Product Compatibility report for the following products:
  • Content Cortex
  • IBM Content Navigator

Limitations for Content Cortex containers

Content Cortex containers have the following limitations:

Content services containers
For detailed list of limitations for Content Platform Engine and IBM Content Foundation, see technote What are the current limitations for containerized deployments of Content Cortex External link opens a new window or tab.
AI Services containers
External MCP clients cannot connect to the MCP server without configuration. Content Cortex standalone deployments require external MCP_SERVER_BASE_URL configuration for external MCP clients. Additionally, non-DCR clients require OAuth client registration with the customer's identity provider.
External MCP Client Object Store Selection
If the MCP client does not support the CS-Object-Store header, you cannot work with different object stores. In that case, the server defaults to the OBJECT_STORE environment variable.
Unsupported Core MCP Server tools
The Core MCP Server tools get_custom_object, get_annotation, and get_document_annotations are not supported in this release. Although these tools remain accessible through the API, they are not intended for use and may cause errors or unexpected behavior in workspace operations. Avoid using these tools until they are officially supported in a future release. For a complete list of supported MCP Server tools, see MCP Server tools reference.