Apache Pinot MCP Server

What the code does

We read the source, 2 h ago · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add mcp-pinot -- uvx mcp-pinot-server

{
  "mcpServers": {
    "mcp-pinot": {
      "command": "uvx",
      "args": [
        "mcp-pinot-server"
      ]
    }
  }
}

[mcp_servers.mcp-pinot]
command = "uvx"
args = ["mcp-pinot-server"]

{
  "mcpServers": {
    "mcp-pinot": {
      "command": "uvx",
      "args": [
        "mcp-pinot-server"
      ]
    }
  }
}

{
  "servers": {
    "mcp-pinot": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "mcp-pinot-server"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: PINOT_CONTROLLER_URL (HTTP(S) endpoint of the Pinot Controller), PINOT_BROKER_URL (HTTP(S) endpoint of the Pinot Broker), PINOT_USERNAME (Optional Pinot basic-auth username), PINOT_PASSWORD (Optional Pinot basic-auth password), PINOT_TOKEN (Optional Pinot bearer token. Overrides username and password when set), PINOT_USE_MSQE (Whether to enable Pinot multi-stage query engine support), MCP_TRANSPORT (Transport mode: 'stdio' (default, for desktop clients) or 'http'), AUTH_PROVIDER (Inbound auth provider for HTTP transport (e.g. 'oauth'); required to bind a non-loopback host).