File tree Expand file tree Collapse file tree
docs/configuration/holmesgpt Expand file tree Collapse file tree Original file line number Diff line number Diff line change @@ -10,6 +10,7 @@ AI Analysis
1010 builtin_toolsets
1111 permissions
1212 custom_toolsets
13+ remote_mcp_servers
1314
1415Why use HolmesGPT?
1516^^^^^^^^^^^^^^^^^^^
@@ -371,3 +372,14 @@ Custom toolsets
371372
372373Custom toolsets are created through your Helm values file and you can find instructions
373374to :doc: `write your own toolsets here <builtin_toolsets >`.
375+
376+ Remote MCP servers
377+ ---------------------
378+
379+ .. warning ::
380+
381+ Remote MCP servers are in **Tech Preview ** stage.
382+
383+ Remote MCP server connections are configured through your Helm values file.
384+ For detailed instructions, refer to the :doc: `Connecting to Remote MCP Servers <remote_mcp_servers >` guide.
385+
Original file line number Diff line number Diff line change 1+ Remote MCP Servers
2+ ====================
3+
4+ .. warning ::
5+
6+ Remote MCP servers are in **Tech Preview ** stage.
7+
8+
9+ HolmesGPT can integrate with remote MCP servers using SSE mode.
10+ This capability enables HolmesGPT to access external data sources and tools in real time.
11+ This guide provides step-by-step instructions for configuring HolmesGPT to connect with remote MCP servers over SSE.
12+
13+ Example : MCP server configuration
14+ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
15+
16+ .. md-tab-set ::
17+
18+ .. md-tab-item :: Robusta Helm Chart
19+
20+ **Helm Values: **
21+
22+ .. code-block :: yaml
23+
24+ holmes :
25+ mcp_servers :
26+ mcp_server_1 :
27+ # human-readable description of the mcp server (this is not seen by the AI model - its just for users)
28+ description : " Remote mcp server"
29+ url : " http://example.com:8000/sse"
30+
31+ mcp_server_2 :
32+ description : " MCP server that runs in my cluster"
33+ url : " http://<service-name>.<namespace>.svc.cluster.local:<service-port>"
34+ config :
35+ headers :
36+ key : " {{ env.my_mcp_server_key }}" # You can use holmes environment variables as headers for the MCP server requests.
37+
38+ Update your Helm values with the provided YAML configuration, then apply the changes with Helm upgrade:
39+
40+ .. code-block :: bash
41+
42+ helm upgrade robusta robusta/robusta --values=generated_values.yaml --set clusterName=< YOUR_CLUSTER_NAME>
43+
44+
45+
46+
You can’t perform that action at this time.
0 commit comments