Doris MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_HOST | Yes | Database hostname | |
| DB_PORT | No | Database port | 9030 |
| DB_USER | Yes | Database username | |
| LOG_DIR | No | Directory for log files | ./logs |
| LOG_LEVEL | No | Log level (e.g., INFO, DEBUG, WARNING, ERROR) | INFO |
| DB_DATABASE | Yes | Default database name | |
| DB_PASSWORD | Yes | Database password | |
| SERVER_HOST | No | Host address the server listens on | 0.0.0.0 |
| SERVER_PORT | No | Port the server listens on | 3000 |
| ALLOWED_ORIGINS | No | CORS allowed origins (comma-separated, * allows all) | |
| CONSOLE_LOGGING | No | Whether to output logs to the console | false |
| MCP_ALLOW_CREDENTIALS | No | Whether to allow CORS credentials | false |
| ENABLE_SQL_SECURITY_CHECK | No | Whether to enable security checks for SQL queries |
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 |
|---|---|
| exec_queryB | [Function Description]: Execute SQL query and return result command (executed by the client). [Parameter Content]:
|
| get_table_schemaB | [Function Description]: Get detailed structure information of the specified table (columns, types, comments, etc.). [Parameter Content]:
|
| get_db_table_listB | [Function Description]: Get a list of all table names in the specified database. [Parameter Content]:
|
| get_db_listC | [Function Description]: Get a list of all database names on the server. [Parameter Content]:
|
| get_table_commentC | [Function Description]: Get the comment information for the specified table. [Parameter Content]:
|
| get_table_column_commentsC | [Function Description]: Get comment information for all columns in the specified table. [Parameter Content]:
|
| get_table_indexesB | [Function Description]: Get index information for the specified table. [Parameter Content]:
|
| get_recent_audit_logsC | [Function Description]: Get audit log records for a recent period. [Parameter Content]:
|
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 8 tools
Each tool has a clearly distinct purpose with no ambiguity. exec_query handles SQL execution, get_db_list retrieves database names, get_db_table_list lists tables, get_recent_audit_logs fetches logs, and the remaining tools (get_table_column_comments, get_table_comment, get_table_indexes, get_table_schema) each target specific table metadata aspects without overlap.
All tools follow a consistent verb_noun pattern using snake_case. The naming is highly predictable: exec_query, get_db_list, get_db_table_list, get_recent_audit_logs, get_table_column_comments, get_table_comment, get_table_indexes, and get_table_schema all adhere to the same convention.
With 8 tools, this server is well-scoped for database interaction and metadata exploration. Each tool earns its place by covering distinct aspects like query execution, database/table listing, audit logs, and detailed table metadata, without being overly sparse or bloated.
The toolset provides strong coverage for querying and inspecting databases, including CRUD-like operations via exec_query and comprehensive metadata retrieval. Minor gaps exist, such as no explicit tools for creating/dropping databases or tables, but agents can work around this using exec_query for such operations.