Skip to main content
Glama
jommar

mcp-knowledgebase

by jommar

Related Servers

Alternatives to mcp-knowledgebase

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to connect to MySQL databases, execute read-only queries, list tables, and describe table schemas via MCP.
      1
      -
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to query and manage MySQL databases through a structured MCP interface, supporting SQL execution, table inspection, and database operations.
      9
      5 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Provides AI agents a secure MCP interface to a single MySQL or MariaDB database, enabling schema inspection, read-only queries, query planning, and guarded write operations with strict safety controls.
      6
      19 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides read-only access to MySQL databases, enabling schema exploration, table inspection, and safe SELECT query execution via MCP.
      1
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to inspect and query a MySQL database through safe, structured tools, including schema discovery and read-only queries.
      9
      122 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Safe MySQL database exploration for AI agents via MCP, enabling read-only queries and schema inspection with three-layer write protection.
      9
      MIT

    TDQS

    A3.9/5.0

    Scored across 6 tools

    Disambiguation4/5

    Tools mostly target distinct concerns: schema overview, keys, single-table details, table listing, search, and raw query. However, get_schema and describe_table overlap in providing column/key info, which could confuse an agent choosing between them. Overall boundaries are clear enough with careful reading.

    Naming Consistency3/5

    Four tools use the get_ prefix (get_schema, get_keys, get_tables), but describe_table and search_tables use different verbs, and raw_query breaks the pattern entirely. The mix of get_, describe_, search_, and raw_ is readable but not consistent. A unified verb_noun convention would improve predictability.

    Tool Count5/5

    Six tools is a well-scoped count for a database metadata and query server. Each tool covers a distinct aspect of exploration (schema, keys, tables, search, single-table details, raw queries), with no redundant tools. This is within the ideal range.

    Completeness4/5

    The toolset covers the main workflows: understanding schema, relationships, discovering tables, and running read-only queries. Minor gaps exist around indexes, views, or row sampling, but these are not critical for a knowledge base. The core surface is complete for navigation and querying.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues