MariaDB Reader MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MARIADB_HOST | Yes | MariaDB 호스트 주소 | |
| MARIADB_PORT | Yes | MariaDB 포트 번호 (예: "3306") | |
| MARIADB_USER | Yes | MariaDB 사용자 이름 | |
| MARIADB_DATABASE | No | (선택) 기본 데이터베이스 이름 | |
| MARIADB_PASSWORD | Yes | MariaDB 비밀번호 |
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 |
|---|---|
| list_databasesB | 접근 가능한 모든 데이터베이스 목록을 보여줍니다. |
| list_tablesC | 특정 데이터베이스 내의 모든 테이블 목록을 보여줍니다. |
| get_table_schemaB | 특정 테이블의 스키마(컬럼 정의)를 가져옵니다. |
| query_tableC | 특정 테이블에서 데이터를 조회합니다 (제한된 행 반환). |
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 with no overlap: get_table_schema retrieves column definitions, list_databases shows available databases, list_tables enumerates tables within a database, and query_table fetches data from a table. The descriptions clearly differentiate their functions, making misselection unlikely.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., get_table_schema, list_databases, list_tables, query_table). The naming is predictable and readable throughout the set, with no deviations in style.
With 4 tools, the count is reasonable for a database reader server, but it feels slightly thin for covering all typical read operations. While core functions are present, additional tools like querying across tables or advanced filtering might enhance completeness without being excessive.
The tool set covers basic read operations (list databases, list tables, get schema, query data), but there are notable gaps for a database reader. Missing operations include querying with custom SQL, joining tables, or advanced filtering, which could limit agent capabilities in complex scenarios.