sisense

This Sisense MCP Server provides a lightweight, per-session authenticated bridge for LLMs to interact with Sisense data models. It exposes three MCP tools: getDataSources, which retrieves available Sisense data sources or data models; getDataSourceFields, which lists all fields for a specified data source; and buildChart, which converts natural language prompts into chart configurations that render in an MCP Apps iframe when supported by the client. The server supports streaming via HTTP/SSE for compatible clients and derives its public URL from request headers, making it suitable to run behind proxies or tunneling services like ngrok. You can connect using Sisense credentials supplied via URL parameters or environment variables (SISENSE_URL and SISENSE_TOKEN).

Prerequisites:

• Bun >= 1.0.0 (recommended) or Node.js >= 18.0.0
• Sisense instance with API access
• Sisense API token

Installation steps:

1. Ensure Bun (or Node) is installed on your system.
   • Bun: https://bun.sh/
   • Node: https://nodejs.org/
2. Clone the repository or download the source.
3. Install dependencies:
   • bun install (If using Node, run: npm install or yarn install after ensuring the project has a package.json)
4. Start the server in development mode:
   • bun run dev
   • If using Node/npm scripts, ensure a start script is defined, e.g., node dist/server.js or node src/server.js after build.
5. Verify the server is running. The server will typically listen on port 3001 by default and expose health and endpoints as described in the README.

• The server uses per-session authentication via Sisense credentials passed through URL parameters (sisenseUrl and sisenseToken) or via environment variables (SISENSE_URL and SISENSE_TOKEN). If both methods are provided, URL parameters take precedence.
• Recommended environment handling: Do not commit credentials to version control. Use secret managers or vaults in production.
• Do not bind to 0.0.0.0 in production; prefer localhost or a reverse proxy/socket.
• When running behind proxies, the server derives its public base URL from request headers.
• Endpoints of interest include health at /health and visuals at /screenshots/ if supported by the build.
• The three MCP Tools (getDataSources, getDataSourceFields, buildChart) are designed to integrate with Claude and other MCP Apps-enabled clients where buildChart can render an interactive View inside an iframe.