StarTree MCP Server for Apache Pinot
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| test-connectionB | Test Pinot connection and return diagnostics |
| read-queryC | Execute a SELECT query on the Pinot database |
| list-tablesB | List all tables in Pinot |
| table-detailsC | Get table size details |
| segment-listC | List segments for a table |
| index-column-detailsC | Get index/column details for a segment |
| segment-metadata-detailsC | Get metadata for segments of a table |
| tableconfig-schema-detailsC | Get table config and schema |
| create-schemaD | Create a new schema |
| update-schemaC | Update an existing schema |
| get-schemaC | Fetch a schema by name |
| create-table-configD | Create table configuration |
| update-table-configD | Update table configuration |
| get-table-configD | Get table configuration |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| pinot-query | Query Pinot database with MCP Server + Claude |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Every tool has a clearly distinct purpose with no ambiguity. Each tool targets a specific resource (schema, table, segment, query, connection) and action (create, get, list, update, test, read), making it easy for an agent to select the correct tool. For example, 'get-schema' and 'update-schema' are clearly differentiated by their actions on the same resource.
Tool names follow a highly consistent verb-noun pattern throughout, using kebab-case (e.g., create-schema, get-table-config, list-tables). This predictable naming convention enhances readability and makes the tool set easy to navigate. All tools adhere to this style without any deviations or mixed conventions.
With 14 tools, the count is well-scoped for managing Apache Pinot databases, covering essential operations like schema and table configuration, querying, segment management, and diagnostics. Each tool earns its place by addressing a specific need in the domain, avoiding bloat or thin coverage.
The tool set provides complete CRUD/lifecycle coverage for Apache Pinot management, including create, read, update, and list operations for schemas, tables, and segments, plus query execution and connection testing. There are no obvious gaps or dead ends, enabling agents to handle full workflows effectively.