Apache Pinot + MCPHub (mcp.nvim): 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 MCPHub (mcp.nvim), 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 MCPHub (mcp.nvim), 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 MCPHub (mcp.nvim)
- 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
- MCPHub (mcp.nvim) installed and configured
- Compatible operating system (Neovim 0.9+, Windows, macOS, Linux)
Installation
Step 1: Install Apache Pinot
Configuration
Step 2: Configure MCPHub (mcp.nvim)
- Open MCPHub (mcp.nvim) 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 MCPHub (mcp.nvim):
List All Tables
Get overview of available Pinot tables
Ask MCPHub (mcp.nvim): "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 MCPHub (mcp.nvim): "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 MCPHub (mcp.nvim): "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 MCPHub (mcp.nvim): "Create a histogram showing user activity distribution by hour"
Expected Result: Histogram visualization with data aggregated by time buckets
Testing Your Setup
- Launch MCPHub (mcp.nvim)
- 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
Plugin Not Loading or Command Not Found
Symptoms: :MCPHub command not recognized, Plugin not appearing in :PlugStatus, No errors but plugin inactive
Cause: Plugin not properly installed or configuration error
Solution:
- Verify plugin is added to plugin manager configuration
- Run plugin manager install command (:PackerInstall, :PlugInstall, or Lazy auto-install)
- Check for errors in :messages after sourcing config
- Ensure dependencies (plenary.nvim, nui.nvim) are installed
- Restart Neovim completely
MCP Server Won't Start
Symptoms: Server status shows "Error", Red indicator on server, Server immediately stops after starting
Cause: Invalid server configuration or missing dependencies
Solution:
- Verify npx is installed and in PATH: npx --version
- Check MCP server package exists: npx -y @modelcontextprotocol/server-filesystem --help
- Review server configuration in setup() - verify command and args
- Check server logs in MCPHub interface for detailed error messages
- Ensure required environment variables are set (e.g., GITHUB_TOKEN)
- Test server manually in terminal: npx -y @modelcontextprotocol/server-filesystem /path
UI Not Displaying Correctly
Symptoms: Blank window, Garbled text, Layout issues, Missing borders
Cause: Terminal or Neovim rendering issues
Solution:
- Verify Neovim version is 0.9 or higher: nvim --version
- Try different border style in ui.border config ("single", "double", "rounded")
- Check terminal supports Unicode and 256 colors
- Update nui.nvim dependency to latest version
- Test with different colorscheme to rule out theme conflicts
Integration with Avante/CodeCompanion Not Working
Symptoms: AI assistant not seeing MCP tools, Tool calls failing, Integration not recognized
Cause: Integration not enabled or incompatible versions
Solution:
- Verify integration is enabled in config: integrations.avante = true
- Ensure Avante.nvim/CodeCompanion.nvim is installed and loaded
- Check versions are compatible - update both plugins to latest
- Restart Neovim after enabling integration
- Check :checkhealth for integration-specific warnings
Marketplace Not Loading
Symptoms: :MCPHubMarketplace shows empty list, Network error in marketplace, Timeout loading servers
Cause: Network connectivity issues or marketplace service unavailable
Solution:
- Verify internet connectivity
- Check firewall allows HTTPS connections
- Try again later if marketplace service is temporarily down
- Review proxy settings if behind corporate firewall
- Check :messages for detailed network error messages
Project-Local Config Not Loading
Symptoms: .mcphub.json ignored, Project servers not appearing, Only global config loaded
Cause: Config file location or format issues
Solution:
- Verify .mcphub.json is in project root (same directory as .git)
- Check JSON syntax is valid using jsonlint or similar tool
- Ensure file name is exactly .mcphub.json (case-sensitive)
- Restart Neovim after creating/modifying project config
- Check file permissions are readable
Apache Pinot not appearing in MCPHub (mcp.nvim)
Symptoms: Server not listed, Tools not available
Cause: Configuration or installation issue
Solution:
- Verify configuration syntax
- Check Apache Pinot installation
- Restart MCPHub (mcp.nvim)
- Check logs for error messages
Next Steps
Now that Apache Pinot is integrated with MCPHub (mcp.nvim):
- Explore all Apache Pinot capabilities through MCPHub (mcp.nvim)
- Check out other MCP servers that work with MCPHub (mcp.nvim)
- Join the MCP community for tips and support
- Consider contributing to Apache Pinot development
Need Help?
- Search for Apache Pinot documentation
- Check the MCPHub (mcp.nvim) MCP guide
- Join the MCP community discussions