StarRocks MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SR_HOST | Yes | StarRocks 数据库地址 (StarRocks database address) | localhost |
| SR_PORT | Yes | StarRocks 查询端口 (StarRocks query port) | 9030 |
| SR_USER | Yes | 数据库用户名 (Database username) | root |
| CENTRAL_API | No | Expert 服务地址，可选 (Expert service address, optional) | http://127.0.0.1:3002 |
| SR_PASSWORD | No | 数据库密码 (Database password) | |
| PROMETHEUS_HOST | No | Prometheus 地址 (Prometheus address) | localhost |
| PROMETHEUS_PORT | No | Prometheus 端口 (Prometheus port) | 9092 |
| CENTRAL_API_TOKEN | No | API Token，可选 (API Token, optional) | |
| PROMETHEUS_PROTOCOL | No | Prometheus 协议 (Prometheus protocol, e.g., http or https) | http |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_query_profileB | 获取指定 Query ID 的执行 Profile，保存到本地文件并返回摘要信息。Profile 文件可用于后续详细分析。 |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently follows a consistent naming pattern. The tool name 'get_query_profile' uses a clear verb_noun structure, which is appropriate and consistent within this minimal set.
A single tool is too few for a server named 'StarRocks MCP Server', which suggests a database or query system. This minimal toolset severely limits functionality and likely leaves many essential operations (e.g., query execution, data management, monitoring) uncovered.
The server is severely incomplete. For a database/query system, only having a tool to get query profiles leaves massive gaps in core operations like running queries, managing data, or accessing system metrics. This toolset does not support basic workflows.