Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion modules/ols-enabling-custom-mcp-server.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@
[role="_abstract"]
Add an additional Model Context Protocol (MCP) server that interfaces with a tool in your environment so that the large language model (LLM) uses the tool to generate answers to your questions.

By default, the cluster introspection feature blocks access to secrets and role-based access control (RBAC) objects. This configuration prevents the leakage of sensitive infrastructure data. Security teams can use this default restriction to validate production deployment safety.
By default, the built-in cluster introspection MCP server blocks access to secrets and role-based access control (RBAC) objects. This configuration prevents the leakage of sensitive infrastructure data. Security teams can use this default restriction to validate production deployment safety.

:FeatureName: The MCP server feature
include::snippets/technology-preview.adoc[]
Expand Down
2 changes: 1 addition & 1 deletion modules/ols-olsconfig-api-specifications.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -482,7 +482,7 @@ The `introspectionEnabled` field in the `OLSConfig` custom resource (CR) is `tru
+
[IMPORTANT]
====
Modifying the MCP server configuration managed by the operator is unsupported. Customizing this configuration requires changing the operator to an unmanaged state. Users who want to customize the MCP server configuration must deploy a standalone MCP server instance independently.
The operator does not support direct modifications to the managed MCP server configuration. To customize this configuration, you must set the operator to an unmanaged state by adding the `operator.openshift.io/managementState: Unmanaged` annotation to the `OLSConfig` custom resource. Alternatively, you can deploy a standalone MCP server instance.
====


Expand Down