Apache Pinot + Msty Studio: 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 Msty Studio, 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 Msty Studio, 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 Msty Studio
- 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
- Msty Studio installed and configured
- Compatible operating system (Desktop (Windows), Desktop (macOS), Desktop (Linux), Web Application)
Installation
Step 1: Install Apache Pinot
Configuration
Step 2: Configure Msty Studio
- Open Msty Studio 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 Msty Studio:
List All Tables
Get overview of available Pinot tables
Ask Msty Studio: "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 Msty Studio: "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 Msty Studio: "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 Msty Studio: "Create a histogram showing user activity distribution by hour"
Expected Result: Histogram visualization with data aggregated by time buckets
Testing Your Setup
- Launch Msty Studio
- 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
MCP Server Not Connecting
Symptoms: Server shows disconnected status, Tool calls fail, Timeout errors
Cause: Invalid configuration or server not accessible
Solution:
- Verify MCP server URL or command is correct
- For STDIO servers, ensure Node.js and npx are installed
- Check firewall settings allow connections
- Review server logs in Toolbox dashboard
- Test server independently outside Msty
Local Model Performance Issues
Symptoms: Slow response times, High memory usage, System freezes
Cause: Model size exceeds hardware capabilities
Solution:
- Use smaller model variants (e.g., Llama 3 8B instead of 70B)
- Enable quantization for reduced memory footprint
- Close other applications to free resources
- Consider using cloud models for complex tasks
- Check system requirements for selected model
Privacy Mode Not Working
Symptoms: Data appears to be sent externally, Telemetry detected, Unexpected network activity
Cause: Cloud models or online MCP servers configured
Solution:
- Ensure using only local models (Llama.cpp-based)
- Configure STDIO MCP servers instead of HTTP/SSE
- Disable internet connection to verify offline capability
- Review Insights dashboard for token usage (should be zero for local)
- Check Privacy settings are configured correctly
Turnstile Workflow Failures
Symptoms: Workflow stops mid-execution, Steps not triggering, Incorrect branching
Cause: Logic errors or MCP server issues
Solution:
- Test each workflow step individually
- Verify all MCP servers in workflow are connected
- Review workflow logic and conditions
- Check Turnstile logs for execution errors
- Simplify complex workflows for debugging
Cross-Device Sync Problems
Symptoms: Settings not syncing, Conversations missing, Inconsistent state
Cause: Sync service issues or Aurum plan not active
Solution:
- Verify Aurum plan is active and current
- Check internet connection on all devices
- Manually trigger sync from settings
- Review sync logs for errors
- Contact support if issues persist
Apache Pinot not appearing in Msty Studio
Symptoms: Server not listed, Tools not available
Cause: Configuration or installation issue
Solution:
- Verify configuration syntax
- Check Apache Pinot installation
- Restart Msty Studio
- Check logs for error messages
Next Steps
Now that Apache Pinot is integrated with Msty Studio:
- Explore all Apache Pinot capabilities through Msty Studio
- Check out other MCP servers that work with Msty Studio
- Join the MCP community for tips and support
- Consider contributing to Apache Pinot development
Need Help?
- Search for Apache Pinot documentation
- Check the Msty Studio MCP guide
- Join the MCP community discussions