# Enabling the MCP Server on Self-Hosted Deployments > Enable the Sisense MCP Server on a self-hosted Sisense deployment: add the sisenseMcp flag to your installer configuration, run the installer or upgrade, and give users the endpoint on your own instance. *Source: https://docs.sisense.com/main/SisenseLinux/mcp-selfhosted.htm* --- Last updated: October 18, 2026 | | | | --- | --- | | [Tier](https://www.sisense.com/pricing/#pricing) | [Deployment](https://docs.sisense.com/main/SisenseLinux/introduction-to-sisense-cloud-managed-services.md#ComparisonofManagedCloudandSelfHosted) | | Enterprise | On-Prem | **Availability:** Self-hosted deployments · Sisense 2026.3.1 and later On self-hosted deployments, the [Sisense MCP Server](https://docs.sisense.com/main/SisenseLinux/mcp-server.md) runs on your own Sisense instance. It is disabled by default and is deployed only after an administrator enables it at install or upgrade. Once enabled, your instance serves the MCP endpoint, and users connect to it with the same OAuth 2.1 sign-in used on Managed Cloud. Note: This topic is for administrators of self-hosted deployments. On Managed Cloud, the MCP Server is hosted by Sisense and is on by default. To connect an AI client after the server is enabled, see [Connecting an AI Agent](https://docs.sisense.com/main/SisenseLinux/mcp-connect-ai-agent.md). ## What Enabling the MCP Server Deploys Enabling the MCP Server adds the following to your deployment: - **oauth-gateway** - Handles the OAuth 2.1 sign-in and issues each user a short-lived, per-user credential. - **mcp-service** - The MCP backend that runs the tools on behalf of the signed-in user. Your existing API gateway is configured to serve the endpoint on your current host at `https:///mcp`. No separate ingress or DNS entry is required. No encryption-key setup is required. The keys the OAuth gateway uses are generated and stored by Sisense automatically. ## Prerequisites - Your deployment is on Sisense 2026.3.1 or later. - The DNS name of your deployment (`application_dns_name`, also known as the system alias) is set to the URL your users use to reach Sisense. See [The DNS Name and the OAuth Sign-In](#DNSName) below. - If multitenancy is enabled on your deployment, review [Limitations](#Limitations) before you begin. ## Enabling the MCP Server 1. Confirm that your deployment is on Sisense 2026.3.1 or later. 2. Open the installer configuration file you deploy with (`config.yaml` or `cluster_config.yaml`), and add the `sisenseMcp` setting under `global:`: [Copy](javascript:void(0);) ``` global:   sisenseMcp:     enabled: true ``` Note: In Sisense 2026.3.x, the default configuration files do not include the `sisenseMcp` setting, so you must add it yourself. If your file already has a `global:` section, add `sisenseMcp` inside it rather than creating a second `global:` section. Indentation matters: a top-level `sisenseMcp:` entry that is not nested under `global:` is ignored. 3. Run the installer or upgrade to apply the change. 4. Verify that the `oauth-gateway` and `mcp-service` pods are running: [Copy](javascript:void(0);) ``` kubectl -n sisense get pods | grep -E 'oauth-gateway|mcp-service' ``` If Sisense is installed in a different namespace, replace `sisense` with your namespace. 5. Under **System Configuration > MCP**, make sure the **Enabled** toggle is on. 6. Give your users the endpoint `https:///mcp` (for example, `https://company.sisense.com/mcp`). See [Connecting an AI Agent](https://docs.sisense.com/main/SisenseLinux/mcp-connect-ai-agent.md). 7. Optional: To use the AI-powered tools (`buildQuery` and `buildChart`), enable Cloud-Linked Features and set up an LLM provider, as described in the prerequisites of [Sisense MCP Server](https://docs.sisense.com/main/SisenseLinux/mcp-server.md). To display interactive charts in Claude, add the CORS entry described in [Interactive Charts in Claude](https://docs.sisense.com/main/SisenseLinux/mcp-connect-ai-agent.md#InteractiveChartsInClaude). ## The DNS Name and the OAuth Sign-In The OAuth gateway builds its issuer and sign-in redirect addresses from your deployment's DNS name (`application_dns_name`, also known as the system alias). Make sure this value is the URL your users actually use to reach Sisense. The MCP endpoint is that URL followed by `/mcp`. If you change the DNS name during an upgrade, the OAuth gateway is restarted automatically so that it picks up the new name. For more information about `application_dns_name`, see [Installing Sisense on Linux](https://docs.sisense.com/main/SisenseLinux/installing-sisense-on-linux.md). ## Deployment Notes - `mcp-service` is an internal service (Kubernetes ClusterIP) and is not exposed outside the cluster. All client traffic reaches it through the `/mcp` endpoint on your existing host. - `mcp-service` runs as a single replica by design. Do not enable autoscaling for it. See [Horizontal Pod Autoscaling (HPA)](https://docs.sisense.com/main/SisenseLinux/horizontal-pod-autoscaling.md). ## Limitations - **Multitenancy:** On self-hosted deployments with multitenancy enabled and more than one tenant, requests to `/mcp` return the Sisense "Page not Found" page instead of reaching the MCP Server, so AI clients cannot connect. There is no workaround. This is fixed in Sisense 2026.4.1. Single-tenant deployments are not affected. ## Troubleshooting [**The MCP endpoint cannot be reached.**](#) Check the following: - The `sisenseMcp` setting is nested under `global:` in your configuration file, with `enabled: true`, and the installer or upgrade was run afterward. - The `oauth-gateway` and `mcp-service` pods are running (see step 4 of [Enabling the MCP Server](#EnablingTheMCPServer)). - The Enabled toggle is on under System Configuration > MCP. - If multitenancy is enabled and the endpoint returns the Sisense "Page not Found" page, see [Limitations](#Limitations). [**Sign-in fails or redirects to the wrong address.**](#) Make sure your deployment's DNS name is set to the URL your users use to reach Sisense. See [The DNS Name and the OAuth Sign-In](#DNSName).