diff --git a/docs/configuration/holmesgpt/index.rst b/docs/configuration/holmesgpt/index.rst
index 31afdfbd8..2e54cb807 100644
--- a/docs/configuration/holmesgpt/index.rst
+++ b/docs/configuration/holmesgpt/index.rst
@@ -10,6 +10,7 @@ AI Analysis
    builtin_toolsets
    permissions
    custom_toolsets
+   remote_mcp_servers
 
 Why use HolmesGPT?
 ^^^^^^^^^^^^^^^^^^^
@@ -371,3 +372,14 @@ Custom toolsets
 
 Custom toolsets are created through your Helm values file and you can find instructions
 to :doc:`write your own toolsets here <builtin_toolsets>`.
+
+Remote MCP servers 
+---------------------
+
+.. warning::
+
+    Remote MCP servers are in **Tech Preview** stage.
+
+Remote MCP server connections are configured through your Helm values file.
+For detailed instructions, refer to the :doc:`Connecting to Remote MCP Servers <remote_mcp_servers>` guide.
+
diff --git a/docs/configuration/holmesgpt/remote_mcp_servers.rst b/docs/configuration/holmesgpt/remote_mcp_servers.rst
new file mode 100644
index 000000000..12f0dc15e
--- /dev/null
+++ b/docs/configuration/holmesgpt/remote_mcp_servers.rst
@@ -0,0 +1,46 @@
+Remote MCP Servers 
+====================
+
+.. warning::
+
+    Remote MCP servers are in **Tech Preview** stage.
+
+
+HolmesGPT can integrate with remote MCP servers using SSE mode.
+This capability enables HolmesGPT to access external data sources and tools in real time.
+This guide provides step-by-step instructions for configuring HolmesGPT to connect with remote MCP servers over SSE.
+
+Example : MCP server configuration
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+.. md-tab-set::
+
+  .. md-tab-item:: Robusta Helm Chart
+
+    **Helm Values:**
+
+    .. code-block:: yaml
+
+      holmes:
+        mcp_servers:
+          mcp_server_1:
+            # human-readable description of the mcp server (this is not seen by the AI model - its just for users)
+            description: "Remote mcp server"
+            url: "http://example.com:8000/sse"
+          
+          mcp_server_2:
+            description: "MCP server that runs in my cluster"
+            url: "http://<service-name>.<namespace>.svc.cluster.local:<service-port>"
+            config:
+              headers:
+                key: "{{ env.my_mcp_server_key }}" # You can use holmes environment variables as headers for the MCP server requests.
+        
+    Update your Helm values with the provided YAML configuration, then apply the changes with Helm upgrade:
+
+    .. code-block:: bash
+
+        helm upgrade robusta robusta/robusta --values=generated_values.yaml --set clusterName=<YOUR_CLUSTER_NAME>
+
+    
+
+