Connecting an AI Agent

Last updated: August 15, 2026

You connect an MCP-compatible AI client to Sisense by adding the hosted endpoint and signing in once with your Sisense credentials. There is nothing to install. Claude, ChatGPT, and Cursor are validated for the Beta. Validation covers connecting and running the tools; whether a client can display a rendered chart depends on MCP Apps support in that client, described under Interactive Charts in Claude below.

1. Get the Endpoint URL

The hosted MCP Server runs at a single Sisense address. There are two ways to tell it which deployment to work against, and both are supported.

Option 1: Name your deployment in the URL. Add a target query parameter set to your Sisense URL:

https://mcp.sisense.com/mcp?target=<your-deployment-url>

The client then connects straight to your deployment with no further prompting. This is the form administrators usually distribute when rolling the connector out to a team, because it settles both the endpoint and the deployment up front and nobody has to know or type their instance URL.

Option 2: Use the base endpoint and choose your deployment on screen. Add the endpoint without a target:

https://mcp.sisense.com/mcp

The first time you connect, Sisense presents a form where you enter your deployment URL before signing in. This suits individual users, and anyone who connects to more than one deployment.

Your Sisense administrator can confirm the exact endpoint and your deployment URL.

On self-hosted deployments, the endpoint is exposed by your own instance and serves that instance directly, so no target parameter is needed:

https://<your-deployment>/mcp

Your administrator provides the exact endpoint.

2. Add It to Your MCP Client

Add the endpoint as a remote (HTTP) MCP server. There are no credentials to enter. Authentication happens in the browser on first use.

{
  "mcpServers": {
    "sisense": {
      "url": "https://<hosted-mcp-endpoint>/mcp?target=<your-deployment-url>"
    }
  }
}

3. Sign In and Approve Access

The first time the agent uses the server, your browser opens a Sisense sign-in page. Sign in with your existing Sisense credentials, including SSO, and approve access. Sisense issues the agent a short-lived credential scoped to you, and you are ready to go.

4. Verify the Connection

Confirm the agent is connected before you rely on it:

1. Check that the Sisense tools appear in your client's tool or connector list.

2. Ask the agent to list your data sources, for example, "List my Sisense data sources."

3. You should see the data models your account can access.

If the tools do not appear or the request fails, see Troubleshooting below.

Switching Deployment or Instance

Each connection is scoped to one deployment and one user.

• To point an agent at a different Sisense deployment, change the target in the endpoint URL. The client prompts you to sign in again for that deployment.

• Signing in as a different user, or connecting to a different instance, also starts a new sign-in. Credentials are never shared between users or deployments.

Interactive Charts in Claude

Claude can render the charts built by buildChart as live, interactive visualizations inside the conversation. For this to work, your administrator must add Claude's content domain to the allowed origins in Admin > Security Settings > CORS Allowed Origins:

https://*.claudemcpcontent.com

Use the subdomain wildcard form. Claude loads each chart from an Anthropic subdomain (for example, https://abc123.claudemcpcontent.com), so the browser origin is a subdomain, not the bare domain. Listing https://claudemcpcontent.com on its own does not match, and the chart stays blocked.

Without this entry, queries and other tools still work, but the interactive chart will not load. Clients that do not support interactive content receive only the narrative insights from the chart, not a rendered chart.

Troubleshooting