Apache Pinot MCP Server

Apache Pinot MCP Server runs locally from a Python package published to PyPI: mcp-pinot-server version 4.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install — the usual command is uvx mcp-pinot-server. It reads these environment variables: PINOT_CONTROLLER_URL, PINOT_BROKER_URL, PINOT_USERNAME, PINOT_PASSWORD (secret), PINOT_TOKEN (secret), PINOT_USE_MSQE, MCP_TRANSPORT and AUTH_PROVIDER; set them in the client's configuration for this server.

Apache Pinot MCP Server runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/startreedata/mcp-pinot:4.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run — the usual command is docker run -i --rm ghcr.io/startreedata/mcp-pinot:4.1.0.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "mcp-pinot": {
      "command": "uvx",
      "args": [
        "mcp-pinot-server"
      ],
      "env": {
        "PINOT_CONTROLLER_URL": "<value>",
        "PINOT_BROKER_URL": "<value>",
        "PINOT_USERNAME": "<value>",
        "PINOT_PASSWORD": "<secret>",
        "PINOT_TOKEN": "<secret>",
        "PINOT_USE_MSQE": "<value>",
        "MCP_TRANSPORT": "<value>",
        "AUTH_PROVIDER": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect