starrocks-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level | INFO |
| STARROCKS_HOST | Yes | StarRocks host | |
| STARROCKS_PORT | No | StarRocks port | 9030 |
| STARROCKS_USER | Yes | Your LDAP username | |
| MAX_QUERY_LENGTH | No | Maximum SQL query length | 10000 |
| STARROCKS_DATABASE | No | Default database | ads |
| STARROCKS_PASSWORD | Yes | Your LDAP password | |
| DEFAULT_QUERY_TIMEOUT_MS | No | Default query timeout (ms) | 30000 |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_queryC | Execute a SQL query against StarRocks and return results. |
| list_databasesA | List all databases in StarRocks |
| list_tablesC | List tables in a database |
| describe_tableB | Get table schema and column information |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: describe_table focuses on schema details, execute_query handles SQL execution, list_databases enumerates databases, and list_tables lists tables within a database. There is no overlap or ambiguity between these functions.
All tool names follow a consistent verb_noun pattern (describe_table, execute_query, list_databases, list_tables) with clear, descriptive verbs and nouns. There are no deviations in naming style.
With 4 tools, the count is reasonable for a database interaction server, covering core operations like listing, describing, and querying. It might be slightly thin for advanced database management, but it's well-scoped for basic functionality.
The tools cover essential read and query operations (list, describe, execute), but there are notable gaps for a database server, such as create/update/delete operations for databases or tables, which could limit agent workflows for full lifecycle management.