Apache Pinot + OpenSumi: Complete MCP Integration

Apache Pinot is a MCP server that MCP server for Apache Pinot real-time analytics database with SQL query capabilities and metadata access.

When integrated with OpenSumi, you can:

• List and inspect Apache Pinot tables
• View and analyze table segments
• Retrieve and analyze table schemas

This guide provides step-by-step instructions to set up Apache Pinot in OpenSumi, including configuration, examples, and troubleshooting.

What You'll Achieve

After completing this setup:

• Apache Pinot will be fully integrated and operational
• You can use Apache Pinot tools directly in OpenSumi
• All Apache Pinot capabilities will be available for your workflows
• Access to 5 different tools

Prerequisites

Before starting, ensure you have:

• Apache Pinot broker hostname
• Apache Pinot broker port
• OpenSumi installed and configured
• Compatible operating system (Web (Browser-based), Electron Desktop, Container (Docker/K8s), Framework Integration)

Installation

Step 1: Install Apache Pinot

Configuration

Step 2: Configure OpenSumi

1. Open OpenSumi settings
2. Navigate to MCP server configuration
3. Add Apache Pinot server with appropriate settings
4. Save and restart if needed

Examples

Once configured, you can use Apache Pinot in OpenSumi:

List All Tables

Get overview of available Pinot tables

Ask OpenSumi: "Show me all the tables available in the Pinot cluster"

Expected Result: List of table names with basic metadata and schema information

Execute Analytics Query

Run SQL query for real-time analytics

Ask OpenSumi: "SELECT COUNT(*) FROM events WHERE timestamp > now() - 3600000"

Expected Result: Query results showing event count for last hour

Analyze Table Structure

Get detailed schema information for a table

Ask OpenSumi: "Show me the schema and structure of the user_events table"

Expected Result: Table schema with column names, types, and index information

Generate Data Visualization

Create histogram plots from query results

Ask OpenSumi: "Create a histogram showing user activity distribution by hour"

Expected Result: Histogram visualization with data aggregated by time buckets

Testing Your Setup

1. Launch OpenSumi
2. Verify Apache Pinot is available in the tools list
3. Test basic Apache Pinot functionality

Troubleshooting

Common Issues

uv Command Not Found

Symptoms: Command not found error, uv: command not found

Cause: uv package manager not installed

Solution:

• Install uv using: curl -LsSf https://astral.sh/uv/install.sh | sh
• Restart terminal or source shell configuration
• Verify installation with: uv --version

Pinot Connection Failed

Symptoms: Connection refused, Broker unreachable, Network timeout

Cause: Invalid Pinot broker configuration or cluster not running

Solution:

• Verify PINOT_BROKER_HOST and PINOT_BROKER_PORT in .env file
• Check Pinot cluster is running and accessible
• Test connection: telnet <broker_host> <broker_port>
• Ensure firewall allows connections to Pinot broker

Environment Variables Not Loaded

Symptoms: Config missing errors, Default values being used

Cause: .env file not found or incorrectly formatted

Solution:

• Create .env file in repository root directory
• Copy from .env.example and modify values
• Ensure no spaces around = in variable assignments
• Restart MCP server after configuration changes

Claude Desktop Not Recognizing Server

Symptoms: Server not appearing, Connection errors in Claude

Cause: Incorrect claude_desktop_config.json configuration

Solution:

• Verify path to uv binary in command field
• Ensure correct path to mcp-pinot repository
• Restart Claude Desktop after configuration changes
• Check Claude Desktop logs for error messages

Dependency Installation Failures

Symptoms: Yarn/npm install errors, Missing packages, Version conflicts

Cause: Incompatible Node.js version or network issues

Solution:

• Ensure Node.js 16+ is installed
• Use yarn for standard installation, npm for lite version
• Clear package cache: yarn cache clean or npm cache clean --force
• Check network connectivity and proxy settings

Workspace Not Loading

Symptoms: Empty workspace, Files not showing, Permission errors

Cause: Incorrect workspace path or permissions

Solution:

• Verify MY_WORKSPACE environment variable is set correctly
• Check file system permissions for workspace directory
• Use absolute path for workspace location
• Default workspace is tools/workspace in repository

VSCode Extension Compatibility

Symptoms: Extension not loading, Extension errors, Missing features

Cause: Extension API incompatibility or missing dependencies

Solution:

• Verify extension is compatible with VSCode extension API used by OpenSumi
• Check extension documentation for known issues
• Try downloading extensions via yarn run download-extension
• Some extensions may require OpenSumi-specific adaptation

WebWorker Compilation Errors (Lite Version)

Symptoms: Compile-worker fails, Language service not working, Syntax highlighting broken

Cause: WebWorker build configuration issues

Solution:

• Run npm run compile-worker before starting
• Ensure all dependencies are installed correctly
• Check browser console for WebWorker loading errors
• Clear browser cache and rebuild

MCP Client Connection Failures

Symptoms: Cannot connect to MCP server, Tool discovery fails, MCP errors in console

Cause: MCP server not running or incorrect configuration

Solution:

• Verify MCP server is running and accessible
• Check MCP server URL in OpenSumi configuration
• Review MCP client integration code for errors
• Check browser/Electron console for detailed error messages

Electron App Not Starting

Symptoms: Electron window not opening, White screen, App crashes on launch

Cause: Electron build issues or IPC communication errors

Solution:

• Ensure Electron dependencies are installed correctly
• Check Electron version compatibility (15+)
• Review IPC communication setup in configuration
• Check Electron dev tools console for errors

Apache Pinot not appearing in OpenSumi

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

• Verify configuration syntax
• Check Apache Pinot installation
• Restart OpenSumi
• Check logs for error messages

Next Steps

Now that Apache Pinot is integrated with OpenSumi:

• Explore all Apache Pinot capabilities through OpenSumi
• Check out other MCP servers that work with OpenSumi
• Join the MCP community for tips and support
• Consider contributing to Apache Pinot development

Need Help?

• Search for Apache Pinot documentation
• Check the OpenSumi MCP guide
• Join the MCP community discussions