Apache Pinot + Roo Code: 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 Roo Code, 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 Roo Code, 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 Roo Code
- 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
- Roo Code installed and configured
- Compatible operating system (Windows, macOS, Linux)
Installation
Step 1: Install Apache Pinot
Configuration
Step 2: Configure Roo Code
-
Locate your configuration file:
- Windows:
%USERPROFILE%\.roo\mcp_settings.json - macOS:
~/.roo/mcp_settings.json - Linux:
~/.roo/mcp_settings.json
- Windows:
-
Add server configuration:
{
"mcpServers": {
"apache-pinot": {
"command": "npx",
"args": ["-y", "apache-pinot"],
"env": {
"PINOT_BROKER_HOST": "localhost",
"PINOT_BROKER_PORT": "9000"
}
}
}
}
- Restart Roo Code
Completely quit and restart Roo Code to load the new configuration.
Examples
Once configured, you can use Apache Pinot in Roo Code:
List All Tables
Get overview of available Pinot tables
Ask Roo Code: "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 Roo Code: "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 Roo Code: "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 Roo Code: "Create a histogram showing user activity distribution by hour"
Expected Result: Histogram visualization with data aggregated by time buckets
Testing Your Setup
- Start a new conversation in Roo Code
- Ask Roo Code to list available tools
- Try using Apache Pinot functionality
Test prompts:
- "Type @ and verify Apache Pinot appears in the tools list"
- "Ask: "Use Apache Pinot to help with my task""
- "Check Roo Code output panel for server connection status"
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
MCP Server Not Connecting
Symptoms: Server not appearing in tools list, Connection timeout, MCP tools unavailable
Cause: Incorrect configuration or server not starting
Solution:
- Verify mcp_settings.json syntax is correct
- Check that Node.js and npx are installed and in PATH
- View Roo Code output panel for error messages
- Test server command manually in terminal: npx -y {server_id}
- Ensure environment variables are properly set
Permission Denied Errors
Symptoms: Cannot execute commands, File access denied, Terminal commands blocked
Cause: Roo Code requires explicit permission for file and command operations
Solution:
- Review and approve permission requests when prompted
- Check VS Code workspace trust settings
- Enable necessary permissions in Roo Code settings
- Verify file and folder permissions on your system
API Key or Model Issues
Symptoms: Authentication failed, Model not responding, No AI completions
Cause: AI model API key not configured or invalid
Solution:
- Verify API key is correctly set in Roo Code settings
- Check API key has sufficient credits/quota
- Test with a different AI model provider
- Review Roo Code output panel for API error details
Custom Mode Not Working with MCP
Symptoms: MCP tools not available in custom mode, Mode cannot access server
Cause: Custom mode configuration does not include MCP tool permissions
Solution:
- Edit custom mode configuration to include MCP tools
- Add "Use MCP" to available tools in mode definition
- Ensure mode has appropriate permissions for external tools
- Test with default mode first to verify MCP server works
Extension Conflicts
Symptoms: Roo Code not responding, VS Code performance issues, Unexpected behavior
Cause: Conflicts with other AI coding extensions
Solution:
- Disable other AI coding extensions (Cline, Continue, etc.)
- Restart VS Code after disabling conflicting extensions
- Check VS Code extension logs for conflict errors
- Use only one AI coding assistant extension at a time
Apache Pinot not appearing in Roo Code
Symptoms: Server not listed, Tools not available
Cause: Configuration or installation issue
Solution:
- Verify configuration syntax
- Check Apache Pinot installation
- Restart Roo Code
- Check logs for error messages
Next Steps
Now that Apache Pinot is integrated with Roo Code:
- Explore all Apache Pinot capabilities through Roo Code
- Check out other MCP servers that work with Roo Code
- Join the MCP community for tips and support
- Consider contributing to Apache Pinot development
Need Help?
- Search for Apache Pinot documentation
- Check the Roo Code MCP guide
- Join the MCP community discussions