Apache Doris MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DORIS_HOST | Yes | The Apache Doris host | |
| DORIS_PORT | Yes | The Apache Doris port | |
| DORIS_USER | Yes | The Apache Doris user | |
| DORIS_PASSWORD | Yes | The Apache Doris password |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| show_databasesA | List all databases in the Doris instance. Returns: List[str]: A list of database names |
| show_tablesA | List all tables in the specified database. Args: database: The database name like: Optional pattern to filter table names Returns: List[Dict]: A list of table information dictionaries |
| execute_queryA | Run a SELECT query against Doris with timeout protection. Args: query: The SQL query to execute Returns: List[Dict]: The query results |
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 3 tools
Each tool has a distinct purpose: executing SELECT queries, listing databases, and listing tables. No overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case (execute_query, show_databases, show_tables), making them predictable.
Three tools is on the low side for a database server, but it's acceptable for a minimal read-only interface. The scope feels thin but not extreme.
The tool set lacks write operations (INSERT, UPDATE, DELETE), DDL commands (CREATE, DROP, ALTER), and metadata queries (DESCRIBE). Significant gaps for a database server.