[ MCP SERVER SUMMARY ]
Apache Pinot MCP server summary
StarTree's MCP server for Apache Pinot lets AI agents query and explore real-time analytics tables. Bifrost governs which Pinot tools and clusters each team can reach and keeps query activity in your gateway audit log.
| Property | Details |
|---|---|
| Company | StarTree |
| Connection type | STDIO |
| Authentication | Pinot cluster credentials (as configured) |
| Package or endpoint | mcp-pinot (StarTree) |
| Capabilities | Realtime analytics queries, Pinot table exploration, Cluster metadata access |
| Official documentation | Apache Pinot MCP documentation |
Before you start
- Access to a Pinot cluster
- Follow StarTree mcp-pinot README for install and env vars
What you can do with Apache Pinot
- Let analysts ask natural-language questions over Pinot via governed MCP tools
- Separate prod and staging Pinot access with different Bifrost clients
- Monitor agent query volume against your Pinot cluster
[ HOW TO CONNECT ]
Connect Apache Pinot to Bifrost in three steps
Install Bifrost
Start the gateway locally or deploy in your VPC.
npx -y @maximhq/bifrost
Add Apache Pinot in MCP Gateway
Open MCP Gateway in the Bifrost dashboard, click New MCP Server, and choose STDIO. Or register via the API below.
• Confirm the current package name and required PINOT_* env vars in the StarTree mcp-pinot README before production use.
• Point Bifrost STDIO env at your controller/broker endpoints.
Point clients at Bifrost /mcp
Configure Claude Desktop, Cursor, or Claude Code to use your Bifrost endpoint with a virtual key instead of connecting directly to Apache Pinot.
{
"mcpServers": {
"bifrost": {
"url": "http://localhost:8080/mcp",
"headers": {
"Authorization": "Bearer vk_your_virtual_key"
}
}
}
}[ EXAMPLE CONFIG ]
Register Apache Pinot via API
Add this MCP client with a POST to /api/mcp/client. See Connecting to MCP Servers for full options.
curl -X POST http://localhost:8080/api/mcp/client \
-H "Content-Type: application/json" \
-d '{
"name": "apache-pinot",
"connection_type": "stdio",
"stdio_config": {
"command": "uvx",
"args": [
"mcp-pinot"
]
},
"tools_to_execute": [
"*"
]
}'[ WHY BIFROST ]
Run Apache Pinot through one governed gateway
Access control
Virtual keys, RBAC, and tool allowlists per team or agent.
Cost governance
Attribute MCP tool spend alongside LLM usage in one view.
Observability
Log every tool call with latency, server, and virtual key metadata.
Credential isolation
Upstream secrets stay in the gateway — not on every laptop.
[ FAQ ]
Common questions
What does the Apache Pinot MCP server do?
Apache Pinot exposes realtime analytics queries, pinot table exploration, cluster metadata access to MCP-compatible AI clients. Bifrost connects to it as an upstream MCP client and exposes approved tools through one governed /mcp endpoint.
How does Apache Pinot authenticate when used with Bifrost?
Apache Pinot uses Pinot cluster credentials (as configured). Store credentials in Bifrost's environment or credential configuration so they stay at the gateway instead of being copied into every AI client.
Can Claude Desktop, Cursor, or Claude Code use Apache Pinot through Bifrost?
Yes. After registering Apache Pinot in Bifrost, point any HTTP MCP-compatible client at the Bifrost /mcp endpoint and authenticate with a virtual key. The client sees only the tools allowed for that key.
[ RELATED SERVERS ]
More MCP integrations
Snowflake
Connect AI agents to Snowflake data and services through Snowflake Labs’ official MCP server.
Honeycomb
Give AI agents access to Honeycomb observability data for investigating production systems, traces, and telemetry.
Anytype
An MCP server enabling AI assistants to interact with Anytype - a local and collaborative wiki - to organize objects, lists, and more through natural language.