@@ -10,7 +10,7 @@ description:
1010Use the MCPToolConfig Custom Resource Definition (CRD) to centrally manage which
1111tools an MCP server exposes, and optionally rename tools or override their
1212descriptions. You reference the configuration from an MCPServer using the
13- toolConfigRef field.
13+ ` toolConfigRef ` field.
1414
1515- toolsFilter: allow‑list the tools to expose.
1616- toolsOverride: rename tools and/or change their descriptions.
@@ -19,13 +19,6 @@ toolConfigRef field.
1919- Precedence: toolConfigRef takes precedence over the deprecated spec.tools
2020 field on MCPServer.
2121
22- ## Prerequisites
23-
24- - ToolHive operator installed. See
25- [ Deploy the operator using Helm] ( ./deploy-operator-helm.md ) .
26- - Permissions to create namespaced resources (and optionally RBAC for servers
27- that need cluster access).
28-
2922## Define a basic tool filter
3023
3124This example exposes only three tools on a server:
@@ -75,12 +68,15 @@ spec:
7568 description : Merge a GitHub pull request
7669` ` `
7770
71+ The key in the ` toolsOverride` object is the _original tool name_, while the
72+ ` name` field contains the _new name_ that clients will see.
73+
7874# # Reference the configuration from an MCP server
7975
8076Add toolConfigRef to your MCPServer. toolConfigRef overrides spec.tools
8177(deprecated).
8278
83- ` ` ` yaml title="mcpserver-with-toolconfig.yaml"
79+ ` ` ` yaml {12-13} title="mcpserver-with-toolconfig.yaml"
8480apiVersion: toolhive.stacklok.dev/v1alpha1
8581kind: MCPServer
8682metadata:
0 commit comments