OLS-2018: updated task topic because there were dev changes. Created conceptual topic

Author: rh-tokeefe

configure/ols-configuring-openshift-lightspeed.adoc

@@ -36,4 +36,5 @@ include::modules/ols-tokens-and-token-quota-limits.adoc[leveloffset=+1]
 include::modules/ols-activating-token-quota-limits.adoc[leveloffset=+2]
 include::modules/ols-about-postgresql-persistence.adoc[leveloffset=+1]
 include::modules/ols-enabling-postgresql-persistence.adoc[leveloffset=+2]
-include::modules/ols-enabling-mcp-server.adoc[leveloffset=+1]
+include::modules/ols-about-mcp-server.adoc[leveloffset=+1]
+include::modules/ols-enabling-mcp-server.adoc[leveloffset=+2]

modules/ols-about-mcp-server.adoc

@@ -0,0 +1,15 @@
+// Module included in the following assemblies:
+// * lightspeed-docs-main/configure/ols-configuring-openshift-lightspeed.adoc
+
+:_mod-docs-content-type: CONCEPT
+[id="about-mcp-server_{context}"]
+= About Model Context Protocol (MCP) server 
+
+An MCP server, or 
+
+A Model Context Protocol (MCP) server is a program that implements the Model Context Protocol, which creates a secure intermediary between a large language model (LLM) and external resources, such as data sources or software applications. The protocol provides a standardized way for an LLM to increase context by requesting and receiving real-time updates from external resources. This functionality transforms the LLM from a static knowledge base into a dynamic system that uses real-time updates to answer questions or complete actions.
+
+:FeatureName: MCP server
+include::snippets/technology-preview.adoc[]
+
+MCP server is disabled by default. To enable the functionality, add the `spec.featureGate.MCPServer` specification to the `OLSConfig` custom resource (CR).

modules/ols-enabling-mcp-server.adoc

@@ -37,22 +37,32 @@ spec:
     - MCPServer <1>
   mcpServers:
     - name: mcp-server-1 <2>
-      transport: sse / streamable_http <3>
       streamableHTTP:
-        url: http://localhost:8080/mcp <4>
-        timeout: 30 <5>
-        sseReadTimeout: 10 <6>
-        headers: 
+        url: http://localhost:8080/mcp <3>
+        timeout: 30
+        sseReadTimeout: 10
+        headers:
           - Authorization: Bearer <token>
           - Content-Type: application/json
           - Accept: application/json
+        enableSSE: true
+    - name: mcp-server-2
+      streamableHTTP:
+        url: http://localhost:8080/mcp
+        timeout: 30 <4>
+        sseReadTimeout: 10 <5>
+        headers:
+          - Authorization: Bearer <token>
+          - Content-Type: application/json
+          - Accept: application/json
+        enableSSE: true <6>
 ----
 <1> Specifies the MCPServer functionality.
 <2> Specifies the name of the MCP server.
-<3> Specifies the transport protocol that the MCP server uses to communicate.
-<4> Specifies the URL path that the MCP server uses to communicate.
-<5> Specifies the time that the MCP server has to respond to a query. If the client does not receive a query within the time specified, the MCP server times out. In this example, the timeout is 30 seconds.
-<6> Specifies the amount of time a client waits for new data from a Server-Sent Events (SSE) connection. If the client does not receive data within that time, the client closes the connection.
+<3> Specifies the URL path that the MCP server uses to communicate.
+<4> Specifies the time that the MCP server has to respond to a query. If the client does not receive a query within the time specified, the MCP server times out. In this example, the timeout is 30 seconds.
+<5> Specifies the amount of time a client waits for new data from a Server-Sent Events (SSE) connection. If the client does not receive data within that time, the client closes the connection.
+<6> When you set `enableSSE` to true the MCP server establishes a one-way channel that the MCP server uses to push updates to the client whenever the server has new information. The default setting is `false`. 
 
 . Click *Save*. 
 +