Skip to content

Commit b856e22

Browse files
committed
basic docs of how to set up remote mcp server
1 parent 8af6d71 commit b856e22

2 files changed

Lines changed: 49 additions & 0 deletions

File tree

docs/configuration/holmesgpt/index.rst

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,7 @@ AI Analysis
1010
builtin_toolsets
1111
permissions
1212
custom_toolsets
13+
remote_mcp_servers
1314

1415
Why use HolmesGPT?
1516
^^^^^^^^^^^^^^^^^^^
@@ -371,3 +372,10 @@ Custom toolsets
371372

372373
Custom toolsets are created through your Helm values file and you can find instructions
373374
to :doc:`write your own toolsets here <builtin_toolsets>`.
375+
376+
Remote MCP servers
377+
-------------------
378+
379+
Remote MCP server connections are configured through your Helm values file.
380+
For detailed instructions, refer to the :doc:`Connecting to Remote MCP Servers <remote_mcp_servers>` guide.
381+
Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
Remote MCP Servers
2+
=====================
3+
4+
HolmesGPT can integrate with remote MCP servers using SSE mode.
5+
This capability enables HolmesGPT to access external data sources and tools in real time.
6+
This guide provides step-by-step instructions for configuring HolmesGPT to connect with remote MCP servers over SSE.
7+
8+
Example : MCP server configuration
9+
^^^^^^^^^^^^^^^^^^^^^^^^^^^
10+
11+
.. md-tab-set::
12+
13+
.. md-tab-item:: Robusta Helm Chart
14+
15+
**Helm Values:**
16+
17+
.. code-block:: yaml
18+
19+
holmes:
20+
toolsets:
21+
mcp_server_1:
22+
# human-readable description of the mcp server (this is not seen by the AI model - its just for users)
23+
description: "Remote mcp server"
24+
url: "http://example.com:8000/sse"
25+
26+
mcp_server_2:
27+
description: "MCP server that runs in my cluster"
28+
url: "http://asdasdasd"
29+
config:
30+
headers:
31+
key: "{{ env.my_mcp_server_key }}" # You can use holmes environment variables as headers for the MCP server requests.
32+
33+
Update your Helm values with the provided YAML configuration, then apply the changes with Helm upgrade:
34+
35+
.. code-block:: bash
36+
37+
helm upgrade robusta robusta/robusta --values=generated_values.yaml --set clusterName=<YOUR_CLUSTER_NAME>
38+
39+
40+
41+

0 commit comments

Comments
 (0)