Configure MCP Pooling
Use these procedures to enable a pooled Hydrolix MCP server deployment and override query routing for individual pools. For an overview of how pooled MCP tenancy works, see MCP Pools.
To set up a pooled MCP deployment:
- Set cluster-wide defaults with the
mcp_hydrolixtunable. - Create an additional pool with
service: mcp-hydrolix. - Optionally, override per-tenant query routing on that pool with a
routing:block.
Enable the MCP server⚓︎
MCP is enabled by default through the mcp_hydrolix tunable. This example sets cluster-wide connection, worker, and transport defaults under spec.mcp_hydrolix.
| Cluster-wide MCP Configuration | |
|---|---|
For the complete list of cluster-wide fields, see The mcp_hydrolix tunable.
Create an mcp-hydrolix pool⚓︎
Create a dedicated MCP pool by adding a pool definition to hydrolixcluster.yaml with the service field set to mcp-hydrolix.
| MCP Pool | |
|---|---|
Without a routing: block, the pool inherits every setting from the cluster-wide mcp_hydrolix tunable.
Override per-pool query routing⚓︎
Add a routing: block to the pool to override a subset of query-routing settings for that pool only. Any unset field inherits the cluster-wide mcp_hydrolix value.
| Per-Pool Routing Override | |
|---|---|
See Per-pool routing overrides for the full list of overridable fields.
Apply the configuration⚓︎
Apply the updated cluster definition with kubectl.
| Apply the Cluster Configuration | |
|---|---|