Skip to main content
Glama
yawlhead91

MariaDB MCP Server

by yawlhead91

Related Servers

Alternatives to MariaDB MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      Provides secure, read-only access to MariaDB/MySQL databases, allowing users to list databases, explore table schemas, and execute SQL queries with built-in security measures.
      4
      40 npm
      4
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with MariaDB databases through schema exploration, query execution, and database statistics. Includes security features like read-only mode, parameterized queries, and connection pooling with support for both JSON and Markdown output formats.
      -
    • F
      license
      A
      quality
      B
      maintenance
      Enables interaction with MariaDB/MySQL databases via MCP, supporting read-only mode, SQL execution, and schema inspection.
      6
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only MySQL/MariaDB schema exploration and safe query cost estimation across multiple instances, with server-enforced write refusal and execution limits.
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables safe interaction with MySQL databases through SELECT queries, table structure inspection, and database schema exploration. Provides read-only access to query data and examine database metadata.
      1
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables safe read-only SQL queries on MySQL/MariaDB databases with multi-domain support, strict selection controls, and audit logging.
      -

    TDQS

    A3.5/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues