SIVIS MCP

TypeScript/Node MCP server for SIVIS backend integrations.

Tool

• sivis_talk_to_data: sends a message to SIVIS Talk to Your Data and returns the final assistant answer plus conversation metadata.

Development

npm install
npm run typecheck
npm run lint
npm test
npm run build

Run stdio transport:

npm run dev

Run Streamable HTTP transport:

npm run dev:http

The HTTP endpoint is available at:

http://localhost:8890/mcp

Run with Docker Compose:

docker compose up --build sivis_mcp

When this service is copied into a larger compose stack that also defines data_visualization, add:

depends_on:
  - data_visualization

Environment

Copy .env.example to .env for local development and provide SIVIS credentials.

Do I need Docker?

It depends on what SIVIS_MCP_SIVIS_BASE_URL points to:

• Remote SIVIS instance — set SIVIS_MCP_SIVIS_BASE_URL=http://sivis.dev.internal.sirenanalytics.com/sivis_mingle and no Docker is needed. The MCP server will hit the hosted SIVIS directly.
• Local Docker stack — if SIVIS_MCP_SIVIS_BASE_URL=http://data_visualization:8080 (the default in .env.example), Docker is required because data_visualization is a container hostname that only resolves inside a Docker network.

NODE_ENV=development
LOG_LEVEL=info
SIVIS_MCP_PORT=8890
SIVIS_MCP_SIVIS_BASE_URL=http://sivis.dev.internal.sirenanalytics.com/sivis_mingle
SIVIS_DOCKER_NETWORK=sivis_dev_environment_default
AUTHORIAN_BASE_URL=http://sivis.dev.internal.sirenanalytics.com/authorian
SIVIS_MCP_AUTH_URL=${AUTHORIAN_BASE_URL}/v1/auth/login
SIVIS_MCP_USERNAME=Admin
SIVIS_MCP_PASSWORD=Adm!n1234