Install MCP Server in Kloudfuse

Deploy the Kloudfuse MCP server directly on your cluster so that any MCP-compatible client can connect to a centrally hosted server without requiring a local Docker installation.

Remote MCP Server

This feature is available starting in Release 3.5.3.

Instead of running the MCP Server locally with Docker, you can deploy it directly on your Kloudfuse cluster. This eliminates the need for local Docker setup and allows any MCP client to connect to a centrally hosted server.

Prerequisites

  • A running Kloudfuse cluster (v3.5.3 or later)

  • Access to modify your custom_values.yaml

  • A Kloudfuse Service Account Token for authentication

Enabling Remote MCP

Add the following section to your custom_values.yaml:

kf-mcp:
  enabled: true
yaml

After updating the configuration, run a Kloudfuse upgrade to apply the changes. Once the upgrade completes, the MCP Server will be available at:

https://<KLOUDFUSE_URL>/mcp

Replace <KLOUDFUSE_URL> with the address of your Kloudfuse instance.

Client Configuration

MCP clients can connect to the remote server using the URL above. All requests must include an authorization header with a valid Kloudfuse Service Account Token.

For example, in Claude Desktop’s claude_desktop_config.json:

{
  "mcpServers": {
    "kf-mcp-<ALIAS>": {
      "type": "http",
      "url": "https://<KLOUDFUSE_URL>/mcp",
      "headers": {
        "Authorization": "Bearer <KLOUDFUSE_SERVICE_TOKEN>"
      }
    }
  }
}
json

Replace the following values:

  • <ALIAS>: A name for this MCP server connection (use a unique name per cluster)

  • <KLOUDFUSE_URL>: Your Kloudfuse instance address

  • <KLOUDFUSE_SERVICE_TOKEN>: A Kloudfuse Service Account Token

Access is scoped to the permissions of the service token used.
To narrow which tools the connection exposes (for example, only apm and logs), append a toolsets query parameter to the URL — see Toolsets.

Using mcp-remote Proxy

If your MCP client does not support remote transport or authorization headers on the client side, you can use the mcp-remote local proxy to connect to the remote MCP Server.

For example, in Claude Desktop’s claude_desktop_config.json:

{
  "mcpServers": {
    "kf-mcp-<ALIAS>": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://<KLOUDFUSE_URL>/mcp",
        "--header",
        "Authorization: Bearer <KLOUDFUSE_SERVICE_TOKEN>"
      ]
    }
  }
}
json

Replace <ALIAS>, <KLOUDFUSE_URL>, and <KLOUDFUSE_SERVICE_TOKEN> with your connection name, Kloudfuse instance address, and service account token.