Apache Pinot + Apify MCP Tester: 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 Apify MCP Tester, 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 Apify MCP Tester, 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 Apify MCP Tester
- 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
- Apify MCP Tester installed and configured
- Compatible operating system (Web Browser)
Installation
Step 1: Install Apache Pinot
Configuration
Step 2: Configure Apify MCP Tester
- Open Apify MCP Tester settings
- Navigate to MCP server configuration
- Add Apache Pinot server with appropriate settings
- Save and restart if needed
Examples
Once configured, you can use Apache Pinot in Apify MCP Tester:
List All Tables
Get overview of available Pinot tables
Ask Apify MCP Tester: "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 Apify MCP Tester: "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 Apify MCP Tester: "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 Apify MCP Tester: "Create a histogram showing user activity distribution by hour"
Expected Result: Histogram visualization with data aggregated by time buckets
Testing Your Setup
- Launch Apify MCP Tester
- Verify Apache Pinot is available in the tools list
- 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
Connection Failed
Symptoms: Cannot connect to server, Timeout errors
Cause: Server configuration or network connectivity issues
Solution:
- Verify server URL is correct and accessible
- Check if server supports chosen transport method (SSE/HTTP)
- Ensure server is running and accepting connections
- Check firewall and network settings
Tools Not Discovered
Symptoms: Empty tools list, Server connected but no capabilities
Cause: Server not properly implementing MCP protocol
Solution:
- Verify server implements MCP protocol correctly
- Check server logs for tool registration issues
- Ensure server is properly configured and initialized
- Test with known working MCP server for comparison
Tool Execution Fails
Symptoms: Tools available but not responding, Error messages during execution
Cause: Server-side errors or parameter issues
Solution:
- Check tool parameter requirements and formats
- Review server logs for execution errors
- Verify required environment variables are set
- Test with simpler tool calls first
Apache Pinot not appearing in Apify MCP Tester
Symptoms: Server not listed, Tools not available
Cause: Configuration or installation issue
Solution:
- Verify configuration syntax
- Check Apache Pinot installation
- Restart Apify MCP Tester
- Check logs for error messages
Next Steps
Now that Apache Pinot is integrated with Apify MCP Tester:
- Explore all Apache Pinot capabilities through Apify MCP Tester
- Check out other MCP servers that work with Apify MCP Tester
- Join the MCP community for tips and support
- Consider contributing to Apache Pinot development
Need Help?
- Search for Apache Pinot documentation
- Check the Apify MCP Tester MCP guide
- Join the MCP community discussions