trackmcp
Back to directory
IBM

data-intelligence-mcp-server

View on GitHub

data-intelligence-mcp-server is a centralized Model Context Protocol (MCP) server that provides a unified gateway for exposing and managing MCP tools across microservices in the Watsonx Data Intelligence ecosystem

5 stars PythonAI & Machine Learning Updated Oct 30, 2025

Documentation

Data Intelligence MCP Server

The IBM Data Intelligence MCP Server provides a modular and scalable implementation of the Model Context Protocol (MCP), purpose-built to integrate with IBM Data Intelligence services. It enables secure and extensible interaction between MCP clients and IBM’s data intelligence capabilities.

For the list of `tools` supported in this version and sample prompts, refer to TOOLS_PROMPTS.md

For the list of `skills` supported in this version and instructions on how to use them, refer to SKILLS_REFERENCE.md

> Note: For MCP clients that don't support `MCP prompts template` registration, manual prompt templates are available in the `PROMPTS_TEMPLATE_SAMPLES/` directory.

mermaid
flowchart LR
    github["data-intelligence-mcp Github"] -- publish --> registry
    registry["PyPi registry"] -- pip install ibm-watsonx-data-intelligence-mcp-server--> server
    subgraph MCP Host
        client["MCP Client"]  server("Data Intelligence MCP Server")
    end
    server -- HTTPS --> runtime("IBM Data Intelligence")
    subgraph id["Services"]
        runtime
    end
    client  server2("Data Intelligence MCP Server") -- HTTPS --> runtime

Resources:


Table of Contents

1. Quick Install - PyPI

    2. Quick Install - uvx

      3. Server

        4. Client Configuration

          5. Configuration

            6. Privacy Policy


            Quick Install - PyPI

            Prerequisites

            • Python 3.11 or higher
            • Data Intelligence SaaS or CPD 5.2.1

            Installation

            Standard Installation

            Use pip/pip3 for standard installation:

            bash
            pip install ibm-watsonx-data-intelligence-mcp-server

            Skills Setup (Optional)

            After installation, you can copy the included skills folder to your location for easy access:

            bash
            wxdi-setup-skills

            This interactive command will:

            • Ask for your confirmation before copying
            • Copy the skills folder to your given location
            • Handle overwrites if the folder already exists

            Quick Install and run - uv

            Prerequisites

            Install and Running

            stdio mode

            bash
            uvx ibm-watsonx-data-intelligence-mcp-server --transport stdio

            http mode

            bash
            uvx ibm-watsonx-data-intelligence-mcp-server

            To setup skills (optional):

            bash
            uvx --from ibm-watsonx-data-intelligence-mcp-server wxdi-setup-skills

            Server

            If you have installed the ibm-watsonx-data-intelligence-mcp-server locally on your host machine and want to connect from a client such as Claude, Copilot, or LMStudio, you can use the stdio mode as described in the examples under the Client Configuration section.

            The server can also be configured and run in http/https mode.

            Refer to Client Settings section on applicable environment variables for http mode. Update as required before starting the server below. Default DI_ENV_MODE is SaaS

            HTTP Mode

            bash
            ibm-watsonx-data-intelligence-mcp-server --transport http --host 0.0.0.0 --port 3000

            HTTPS Mode

            Refer to SERVER_HTTPS.md for detailed HTTPS server configuration and setup.

            stdio Mode

            When configuring the server through Claude, Copilot, or an MCP client in stdio mode, the server does not need to be started separately. The client will invoke the server directly using standard input/output.


            Client Configuration

            Claude Desktop

            Prereq: uv installation guide

            Add the MCP server to your Claude Desktop configuration:

            json
            {
              "mcpServers": {
                "wxdi-mcp-server": {
                  "command": "uvx",
                  "args": ["ibm-watsonx-data-intelligence-mcp-server", "--transport", "stdio"],
                  "env": {
                     "DI_SERVICE_URL": "https://api.dataplatform.cloud.ibm.com",
                     "DI_APIKEY": "",
                     "DI_ENV_MODE": "SaaS",
                     "LOG_FILE_PATH": "/tmp/di-mcp-server-logs"
                  }
                }
              }
            }

            http/https (Remote setup)

            If the MCP server is running on a local/remote server in http/https mode.

            For Cloud SaaS:

            json
            {
              "mcpServers": {
                "wxdi-mcp-server": {
                  "url": "",
                  "type": "http",
                  "headers": {
                    "x-api-key": "your api key from cloud SaaS"
                  }
                }
              }
            }

            For CPD:

            json
            {
              "mcpServers": {
                "wxdi-mcp-server": {
                  "url": "",
                  "type": "http",
                  "headers": {
                    "x-api-key": "your api key from cpd env",
                    "username": ""
                  }
                }
              }
            }

            VS Code Copilot

            Prereq: uv installation guide

            Add the MCP server to your VS Code Copilot MCP configuration:

            json
            {
              "servers": {
                "wxdi-mcp-server": {
                  "command": "uvx",
                  "args": ["ibm-watsonx-data-intelligence-mcp-server", "--transport", "stdio"],
                  "env": {
                     "DI_SERVICE_URL": "https://api.dataplatform.cloud.ibm.com",
                     "DI_APIKEY": "",
                     "DI_ENV_MODE": "SaaS",
                     "LOG_FILE_PATH": "/tmp/di-mcp-server-logs"
                  }
                }
              }
            }

            http/https (Remote setup)

            If the MCP server is running on a local/remote server in http/https mode.

            For Cloud SaaS:

            json
            {
              "servers": {
                "wxdi-mcp-server": {
                  "url": "",
                  "type": "http",
                  "headers": {
                    "x-api-key": "your api key from cloud SaaS"
                  }
                }
              }
            }

            For CPD:

            json
            {
              "servers": {
                "wxdi-mcp-server": {
                  "url": "",
                  "type": "http",
                  "headers": {
                    "x-api-key": "your api key for cpd env",
                    "username": ""
                  }
                }
              }
            }

            Watsonx Orchestrate

            Watsonx Orchestrate + Data Intelligence blog post demonstrates how Watsonx Orchestrate integrates with the MCP Server for automation.

            IBM Bob

            IBM Bob + Data Intelligence blog post demonstrates how IBM Bob integrates with the MCP Server for automation.


            Configuration

            The MCP server can be configured using environment variables or a `.env` file. Copy `.env.example` to `.env` and modify the values as needed.

            Client Settings

            Below client settings are common whether `http` or `stdio` mode

            Environment VariableDefaultDescription
            `DI_SERVICE_URL``None`Base URL for Watsonx Data Intelligence instance. Example: api.dataplatform.cloud.ibm.com for SaaS and cluster url for CPD
            `DI_ENV_MODE``SaaS`Environment mode (`SaaS` or `CPD`)
            `REQUEST_TIMEOUT_S``60`HTTP request timeout in seconds
            `LOG_FILE_PATH``None`Logs will be written here if provided. Mandatory for `stdio` mode
            `DI_CONTEXT``df`Context for URLs returned from tool responses ( `df`, `cpdaas` for DI_ENV_MODE=SaaS; `df`, `cpd` for DI_ENV_MODE=CPD ). url will be appended by query parameter accordingly.`context=df` in the url for example

            Below client settings are only applicable for `stdio` mode

            Environment VariableDefaultDescription
            `DI_APIKEY``None`API key for authentication
            `DI_USERNAME``None`Username (required when using API key for CPD)
            `DI_AUTH_TOKEN``None`Bearer token for alternative to API key

            For `http/https` mode client can send below headers

            HeadersDefaultDescription
            `x-api-key``None`API key related to SaaS/CPD
            `username``None`username for CPD env If API key is provided
            `authorization``None`Bearer token alternative to apikey

            e.g:

            json
            {
              "servers": {
                "wxdi-mcp-server": {
                  "url": "",
                  "type": "http",
                  "headers": {
                    "x-api-key": "your api key from cloud SaaS/cpd"
                  }
                }
              }
            }
            json
            {
              "servers": {
                "wxdi-mcp-server": {
                  "url": "",
                  "type": "http",
                  "headers": {
                    "authorization": "Bearer token"
                  }
                }
              }
            }

            SSL/TLS Configuration

            If running in CPD environment, you might need to configure SSL certificate for client connection. Please look into SSL_CERTIFICATE_GUIDE.md for more details.


            Privacy Policy

            The IBM Watsonx Data Intelligence MCP Server is committed to protecting user privacy and data security.

            • Data Collection: We collect only the data necessary for authentication and service operations (API keys, queries, operational logs)
            • Usage and Storage: Data is processed in-memory and transmitted securely to IBM Data Intelligence services via HTTPS. Local logs are stored only when configured by users. The Server maintains no persistent storage of user data.
            • Third-Party Sharing: Data is shared only with IBM Data Intelligence services (SaaS or Cloud Pak for Data) to fulfill user requests. No data is sold or shared with other third parties.

            For complete details about our data handling practices, security measures, user rights, and compliance information, please read our full Privacy Policy.

            Key Points:

            • Communications:
              • Server ↔ IBM Data Intelligence: HTTPS/TLS encryption
              • MCP Client ↔ Server: stdio or http transport
            • Users have full control over logging and data retention
            • No persistent storage of credentials or user data by the Server
            • Compliant with IBM security and privacy standards

            Frequently asked questions

            What is data-intelligence-mcp-server?

            data-intelligence-mcp-server is data-intelligence-mcp-server is a centralized Model Context Protocol (MCP) server that provides a unified gateway for exposing and managing MCP tools across microservices in the Watsonx Data Intelligence ecosystem

            How do I install data-intelligence-mcp-server?

            Open the GitHub repository and follow its README. Most MCP servers are added to your client's MCP config, then called by your agent.

            Is data-intelligence-mcp-server open source?

            Yes — it is hosted on GitHub at https://github.com/IBM/data-intelligence-mcp-server and has 5 stars.

            Related MCP tools

            Run your own MCP server? See who uses it and what to fix.

            Measure it with TrackMCP