The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Sisense MCP Server listing page.
A Model Context Protocol (MCP) server that provides integration with Sisense analytics platform. This server enables LLMs to interact with Sisense data models and create charts programmatically.
streamable-http) for HTTP-based MCP clients (for example Claude Desktop, Cursor)getDataSources: Retrieve Sisense data sources (or data models)getDataSourceFields: List all available fields for a specific data sourcebuildChart: Build charts from natural language promptsbuildQuery (optional): Run analytics queries when TOOL_BUILD_QUERY_ENABLED / toolBuildQueryEnabled is enabledbuildChart exposes an interactive View that renders the chart in an iframe within the app..env, run, MCP client setupnpm)dev, build, start, tests): the bun package is a devDependency, so after npm install or bun install the Bun binary is available under node_modules/.bin—a global Bun install is not required. A global Bun install is optional.buildChart and buildQuery. See Generative AI (Cloud-Linked Features). This is separate from your MCP client's LLM (e.g. Claude in Cursor).bun install / npm install via postinstall)Start the server:
Sessions are in-memory — chart state is lost if the server restarts.
The server prints something like the following (port defaults to 3001, or PORT if set):
Use an MCP streamable HTTP URL. For Cursor, Claude Desktop, and similar clients, add a server entry with the MCP path (not a shell command such as bun run dev or npm run dev).
If SISENSE_URL and SISENSE_TOKEN are set in the server environment (for example in .env loaded by the process that runs bun run dev or npm run dev), the client URL does not need to include credentials:
Note: Depending on your network or client environment, the localhost HTTP setup may not connect. In those cases, you will need to expose your local server publicly via HTTPS using a proxy service such as ngrok. Point the client at your HTTPS tunnel URL with the same /mcp path (and query parameters if you are not using server env credentials).
Credentials: If you do not use server env vars, put sisenseUrl and sisenseToken on the MCP URL as query parameters (URL params take precedence over env when both are present). Always percent-encode each value — see Configuration: URL encoding for details and examples.
Alternative connection patterns (placeholders only; use encoded values for real credentials):
With SISENSE_URL and SISENSE_TOKEN in the server environment only:
Behind a public HTTPS tunnel (example):
In MCP App mode (the default), Anthropic Claude renders charts inside the MCP content UI—on claude.ai or Claude Desktop. The browser loads your Sisense instance from origins under *.claudemcpcontent.com, so Sisense must allow those origins or the widget fails with a network or CORS error.
In your Sisense instance, go to Admin → Security Settings → CORS Allowed Origins and add:
https://*.claudemcpcontent.com
Use this subdomain wildcard form. A single origin such as https://claudemcpcontent.com (no *.) may not match the actual frame origins and charts can still fail to load.
More context: FAQ: Claude MCP App charts and CORS.
| Parameter | Description |
|---|---|
sisenseUrl | Full URL to your Sisense instance (e.g., https://instance.sisense.com). In the query string, pass the value percent-encoded. |
sisenseToken | Sisense API authentication token. In the query string, pass the value percent-encoded (required if the token contains &, =, +, etc.). |
PORT | (Optional) Server port, defaults to 3001 |
The server automatically derives its public base URL from request headers, so it works correctly behind proxies like ngrok. For how to build encoded MCP URLs, see URL encoding for query parameters.
Defaults suit most setups; change flags when you need a specific client behavior. For when to use each flag, copy-paste URL patterns, and env vs query string, see docs/guides/configuration.md.
These query params override the corresponding env vars on a per-connection basis. Accepted values: true, false, 1, 0 (case-insensitive).
| Query parameter | Env var equivalent | Default | Description |
|---|---|---|---|
mcpAppEnabled | MCP_APP_ENABLED | true | Renders the chart in an interactive app UI (supported in Claude); set to false for tool mode (image/screenshot output) |
toolBuildQueryEnabled | TOOL_BUILD_QUERY_ENABLED | false | Enable the buildQuery tool for executing analytics queries |
toolBuildChartNarrativeEnabled | TOOL_BUILD_CHART_NARRATIVE_ENABLED | true | Include NLG narrative/insights in the build chart tool response |
Example URL with all three overrides (encode sisenseUrl and sisenseToken values when they are not simple alphanumeric placeholders):
⚠️ NEVER commit credentials to version control
⚠️ Use secret managers or vaults - NOT environment variables in production
⚠️ NEVER bind to 0.0.0.0 in production - use 127.0.0.1 or Unix socket
⚠️ Recommended: Use dev or staging Sisense when you have them. Autonomous AI clients can issue many API calls, and prompts can be ambiguous. Non-production reduces the impact of mistakes and surprises.
⚠️ Enable authentication - never run without auth
⚠️ Approve EVERY tool call - review all parameters before execution
⚠️ Create dedicated Sisense service account with minimum required permissions
⚠️ Rotate credentials regularly (every 90 days recommended)