Sisense MCP Server

Name: Sisense MCP Server
Author: sisense

by sisenseversion 0.2.2i★ –iRuns on your computer

Registry nameio.github.sisense/sisense-mcp-server

Install

Overview

Description from the maker (original English)

MCP server leveraging Sisense Intelligence for actionable insights and analytics.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Marketing & social media
You need to fill in: SISENSE_URL, SISENSE_TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: SISENSE_URL, SISENSE_TOKEN

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "sisense": {
      "command": "npx",
      "args": [
        "-y",
        "@sisense/mcp-server"
      ],
      "env": {
        "SISENSE_URL": "your-value",
        "SISENSE_TOKEN": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add sisense --env SISENSE_URL=your-value --env SISENSE_TOKEN=your-value -- npx -y @sisense/mcp-server

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "sisense": {
      "command": "npx",
      "args": [
        "-y",
        "@sisense/mcp-server"
      ],
      "env": {
        "SISENSE_URL": "your-value",
        "SISENSE_TOKEN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "sisense": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@sisense/mcp-server"
      ],
      "env": {
        "SISENSE_URL": "your-value",
        "SISENSE_TOKEN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

SISENSE_URL required env
URL of the Sisense instance
SISENSE_TOKEN secret required env
Bearer token for the Sisense instance

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account sisense, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Marketing & social mediai

More stars than 0% of the other 2970 servers in this category
Published to the registry more recently than 3% of the other 2970 servers in this category
Basic checks equal to or better than 100% of the other 2970 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Sisense MCP Server safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: SISENSE_URL, SISENSE_TOKEN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.2) reached the registry 8 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

MCP YouTube Transcript

by jkawamoto

An MCP server retrieving transcripts of YouTube videos

Runs on your computer★ 495MITUpdated 9 days ago

Install

Google Analytics MCP

by surendranb

GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.

Runs on your computer★ 244MITUpdated 9 days ago

Install

BibiGPT YouTube Video Summarizer

by JimmyLv

AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.

Runs in the cloud★ 137MITUpdated 10 days ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Sisense MCP Server

[!WARNING]

Deprecated. This repository is no longer maintained and will be archived.

The Sisense MCP Server is now a hosted endpoint with OAuth 2.1, available in Sisense 2026.3.1.

See the Sisense MCP Server documentation to set it up.

This repository will not receive further features or fixes.

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.

Features

Transport: Streamable HTTP (streamable-http) for HTTP-based MCP clients (for example Claude Desktop, Cursor)
MCP tools (three by default; optional fourth when enabled):
getDataSources: Retrieve Sisense data sources (or data models)
getDataSourceFields: List all available fields for a specific data source
buildChart: Build charts from natural language prompts
buildQuery (optional): Run analytics queries when TOOL_BUILD_QUERY_ENABLED / toolBuildQueryEnabled is enabled
MCP Apps: When used in MCP Apps–capable clients (for example Claude), buildChart exposes an interactive View that renders the chart in an iframe within the app.
Per-session authentication: Sisense credentials via URL parameters and/or server environment variables
TypeScript: Full type safety and modern ESM support
Lightweight: Pure Node.js HTTP server, no heavy frameworks
Fast: Optimized for Bun runtime, also runs on Node.js

Documentation

Quick start — clone, .env, run, MCP client setup
Configuration — credentials, tunneling, feature flags, URL examples
FAQ — common questions and troubleshooting
Usage examples — prompts and workflows

Prerequisites

Node.js >= 18.0.0 (required for local development and npm)
Bun for running project scripts (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.
Sisense instance with API access
Sisense API token
Cloud-Linked Features enabled on your Sisense instance (and an LLM provider configured if using Bring Your Own Key (BYOK)). Required for natural-language tools such as buildChart and buildQuery. See Generative AI (Cloud-Linked Features). This is separate from your MCP client's LLM (e.g. Claude in Cursor).
Playwright Chromium (installed automatically by bun install / npm install via postinstall)

Installation

bun install

or

npm install

Usage

Start the server:

# Development mode (hot reload)

bun run dev

or

npm run dev

Production mode

bun run build && bun run start

or

npm run build && npm run start

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):

Sisense MCP Server running on http://localhost:3001

Connect with: http://localhost:3001/mcp?sisenseUrl= &sisenseToken= Or set SISENSE_URL and SISENSE_TOKEN in the environment and use http://localhost:3001/mcp

Optional feature-flag query params (override env vars per connection): mcpAppEnabled=true|false, toolBuildQueryEnabled=true|false, toolBuildChartNarrativeEnabled=true|false

Endpoints: Health: http://localhost:3001/health Screenshots: http://localhost:3001/screenshots/

Connecting your MCP client

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:

"mcpServers": { "sisense-analytics": { "url": "http://localhost:3001/mcp" } } }

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):

http://localhost:3001/mcp?sisenseUrl=https://your-instance.sisense.com&sisenseToken=your-api-token

With SISENSE_URL and SISENSE_TOKEN in the server environment only:

http://localhost:3001/mcp

Behind a public HTTPS tunnel (example):

https://your-ngrok-url.ngrok-free.app/mcp?sisenseUrl=https://your-instance.sisense.com&sisenseToken=your-api-token

Claude (claude.ai and Desktop): Sisense CORS for interactive charts

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.

Configuration

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.

Optional feature-flag 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):

http://localhost:3001/mcp?sisenseUrl=https://your-instance.sisense.com&sisenseToken=your-api-token&mcpAppEnabled=false&toolBuildQueryEnabled=true&toolBuildChartNarrativeEnabled=false

Development

# Run server in development mode with hot reload

bun run dev

or npm run dev

Build the project (View + server)

bun run build

or npm run build

Build only the analytics View (dist/view.html)

bun run build:view

or npm run build:view

Run tests

bun test

or npm test (same as npm run test)

Type checking

bun run type-check

or npm run type-check

Lint

bun run lint

or npm run lint

Security Considerations

⚠️ 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)

Sisense MCP Server

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Marketing & social mediai

Common questions

Alternatives

MCP YouTube Transcript

Google Analytics MCP

BibiGPT YouTube Video Summarizer

README from the maker

Sisense MCP Server

Features

Documentation

Prerequisites

Installation

or

Usage

or

Production mode

or

Connecting your MCP client

Claude (claude.ai and Desktop): Sisense CORS for interactive charts

Configuration

Optional feature-flag query parameters

Development

or npm run dev

Build the project (View + server)

or npm run build

Build only the analytics View (dist/view.html)

or npm run build:view

Run tests

or npm test (same as npm run test)

Type checking

or npm run type-check

Lint

or npm run lint

Security Considerations