Apache Pinot + Cline: 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 Cline, 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 Cline, 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 Cline
• 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
• Cline installed and configured
• Compatible operating system (Windows, macOS, Linux)

Installation

Step 1: Install Apache Pinot

Configuration

Step 2: Configure Cline

1. Open Cline 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 Cline:

List All Tables

Get overview of available Pinot tables

Ask Cline: "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 Cline: "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 Cline: "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 Cline: "Create a histogram showing user activity distribution by hour"

Expected Result: Histogram visualization with data aggregated by time buckets

Testing Your Setup

1. Launch Cline
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

Extension Not Loading

Symptoms: Cline extension not appearing, Command palette empty

Cause: Extension installation or VS Code configuration issue

Solution:

• Verify extension is properly installed via Extensions panel
• Check VS Code version compatibility
• Reload VS Code window or restart application
• Check VS Code developer console for error messages

MCP Server Not Found

Symptoms: Server command not found, Tools unavailable in Cline

Cause: Server not installed or not accessible from VS Code

Solution:

• Verify MCP server installation and PATH configuration
• Test server command from VS Code integrated terminal
• Use absolute path to server executable in configuration
• Check server executable permissions

Configuration Not Applied

Symptoms: Settings changes not taking effect, Old configuration persisting

Cause: VS Code settings not reloaded or invalid configuration

Solution:

• Reload VS Code window after configuration changes
• Verify JSON syntax in settings.json is valid
• Check Cline extension settings panel for errors
• Review VS Code developer console for configuration warnings

Tool Execution Fails

Symptoms: MCP tools available but not working, Error during tool execution

Cause: Server configuration or environment issues

Solution:

• Verify environment variables are set correctly
• Check server logs for execution errors
• Test server functionality outside of VS Code
• Ensure all required dependencies are installed

Apache Pinot not appearing in Cline

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

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

Next Steps

Now that Apache Pinot is integrated with Cline:

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

Need Help?

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