MariaDB MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Set logging level (DEBUG, INFO, WARNING, ERROR, CRITICAL) | INFO |
| MARIADB_HOST | Yes | The MariaDB server host | |
| MARIADB_PORT | Yes | The MariaDB server port | |
| MARIADB_USER | Yes | The MariaDB username | |
| MARIADB_DATABASE | Yes | The MariaDB database name | |
| MARIADB_PASSWORD | Yes | The MariaDB 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| reload_configB | Reload configuration from environment variables and .env file. |
| list_databasesB | List all accessible databases in the MariaDB server. |
| list_tablesB | List all tables in a specific database. |
| get_table_schemaB | Get the schema/structure of a specific table. |
| execute_sqlB | Execute a read-only SQL query and return 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 5 tools
Each tool has a clearly distinct purpose with no overlap: execute_sql for queries, get_table_schema for metadata, list_databases and list_tables for discovery, and reload_config for server management. An agent can easily distinguish between them without confusion.
All tools follow a consistent verb_noun pattern using snake_case (e.g., execute_sql, get_table_schema). The naming is predictable and readable throughout the set, with no deviations in style.
With 5 tools, the count is reasonable and well-scoped for a database server, covering core operations like querying, schema inspection, and listing. It's slightly lean but functional, with no obvious bloat or thinness.
The tools cover read operations and metadata well, but there are notable gaps for a full database lifecycle: no create/update/delete operations for databases, tables, or data. This limits agents to read-only and discovery tasks, which may cause failures in broader workflows.