# Sisense MCP server > Query Sisense data in natural language and build charts, dashboards and Pulse workflows under Sisense governance. - Listing: https://mcp.tc/i/sisense - Connect: use the server's own URL `https://mcp.sisense.com/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint. - Type: remote (Streamable HTTP) - Auth: OAuth sign-in - Category: [Data & Analytics](https://mcp.tc/c/analytics) - Vendor: Sisense - Homepage: ## About Connects AI agents to a Sisense instance. Agents can list data models and sources, inspect fields and measures, ask questions in plain language that Sisense turns into governed queries against the semantic model, and build and refine charts. Pulses can be listed, inspected and run on demand. The hosted endpoint runs over streamable HTTP. Users sign in through OAuth 2.1 with their existing Sisense credentials, including SSO, and every request runs with that user's permissions. No shared API key is used. Managed Cloud has it enabled by default; self-hosted deployments need an administrator to enable it. ## What it can do - List data models and data sources you can access - Inspect fields, measures and formulas before querying - Ask natural language questions answered as governed queries - Build charts and change type, title, sorting or styling - Chain analysis across steps within a session - List, inspect and run Pulses on demand ## Example prompts - "Which data models can I access in Sisense?" - "Show revenue by region for last quarter as a bar chart" - "Change that chart to a line chart and sort by date" - "Run my weekly sales Pulse and tell me if the condition is met" ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport http sisense https://mcp.sisense.com/mcp ``` 2. Start Claude Code, type `/mcp`, pick **sisense** and choose **Authenticate**. A browser window opens for the Sisense sign-in. Add `--scope user` to make it available in every project, not just this one. ### Claude Desktop 1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**. 2. Name it **Sisense** and paste this URL: ```url https://mcp.sisense.com/mcp ``` 3. Click **Add**, then **Connect**, and sign in when Sisense asks. Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too. ### claude.ai 1. Open the connector form on claude.ai. This button fills in the name and URL for you: [Add to claude.ai]() (opens connector settings) 2. Check that the URL reads `https://mcp.sisense.com/mcp` and click **Add**. 3. Click **Connect** and sign in when Sisense asks. Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**. ### ChatGPT 1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**. 2. Enter a name for the server. 3. Under **Connection**, paste `https://mcp.sisense.com/mcp` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to Sisense to sign in. 4. Check **I understand and want to continue**, then select **Create as a plugin**. Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can). ### Cursor [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```json { "mcpServers": { "sisense": { "url": "https://mcp.sisense.com/mcp" } } } ``` Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in. ### VS Code [Install in VS Code]() (opens VS Code) Or from a terminal: ```bash code --add-mcp '{"name":"sisense","type":"http","url":"https://mcp.sisense.com/mcp"}' ``` Or commit it to the repo in `.vscode/mcp.json`: `.vscode/mcp.json`: ```json { "servers": { "sisense": { "type": "http", "url": "https://mcp.sisense.com/mcp" } } } ``` VS Code asks you to sign in the first time the server starts. ### Devin Desktop 1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows): `mcp_config.json`: ```json { "mcpServers": { "sisense": { "serverUrl": "https://mcp.sisense.com/mcp" } } } ``` 2. Refresh the MCP server list in Cascade and sign in when asked. Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers. ### Codex ```bash codex mcp add sisense --url https://mcp.sisense.com/mcp codex mcp login sisense ``` Or edit `~/.codex/config.toml` directly: `config.toml`: ```toml [mcp_servers.sisense] url = "https://mcp.sisense.com/mcp" ``` ### Gemini CLI ```bash gemini mcp add --transport http sisense https://mcp.sisense.com/mcp ``` Then, inside Gemini CLI, run `/mcp auth sisense` to sign in. This adds it to the current project. Add `-s user` to use it everywhere. ### Any client Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file. ```json { "mcpServers": { "sisense": { "type": "http", "url": "https://mcp.sisense.com/mcp" } } } ``` Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE. Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.sisense.com/mcp`. ## Details - Server version: 1.0.0 - Last checked: 2026-11-15 (reachable, asks for credentials) - Listed: 2026-11-02 - Updated: 2026-11-02 --- Source: https://mcp.tc/i/sisense (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report