Skip to main content
Glama

Related Servers

Alternatives to MCP Firebird

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that provides read-only access to Firebird databases, enabling LLMs to inspect database schemas and execute read-only queries.
      10 npm
      8
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables Large Language Models like Claude to access, query, analyze, and manage Firebird SQL databases with support for schema inspection, performance analysis, and database operations through the Model Context Protocol.
      882 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that enables AI assistants to execute SQL queries, list tables, and manage connections to external Firebird databases with automatic diagnostics and multilingual support.
      5
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server for Firebird databases intended for local use. It reads connection details from FlameRobin's fr_databases.conf so no extra configuration is needed — if you have FlameRobin set up with your Firebird databases, this server works out of the box.
      29
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      This server enables Claude to directly interact with SQLite, SQL Server, PostgreSQL, and MySQL databases through the Model Context Protocol, allowing for query execution, table management, and data export capabilities.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server that enables LLMs like Claude to interact with Microsoft SQL Server databases through natural language, supporting queries, data manipulation, and table management.
      8
      1,952 npm
      MIT

    TDQS

    B3.4/5.0

    Scored across 32 tools

    Disambiguation4/5

    Most tools target a clear resource+action (describe-table vs list-tables vs get-table-data). A few boundaries blur: get-server-info advertises 'its available tools' overlapping list-available-tools, and three trigger tools (list-triggers, get-table-triggers, describe-trigger) require careful reading to distinguish.

    Naming Consistency4/5

    Nearly all tools follow a predictable kebab-case verb_noun pattern (get-table-indexes, describe-table, list-procedures). Minor deviations: subscribe_to_event/unsubscribe_from_event use snake_case, and system-health-check/echo break the verb_noun shape.

    Tool Count3/5

    32 tools is on the heavy side, though the broad Firebird object surface (tables, procedures, triggers, functions, packages, events) justifies many. Redundancies like echo and the server-info/list-tools overlap make the set feel padded beyond what the domain strictly needs.

    Completeness4/5

    Strong read/describe coverage across tables, procedures, triggers, functions, packages, and events, plus query execution and analysis. Gaps remain for other Firebird objects (views, domains, generators/sequences, exceptions) and any DDL lifecycle, but core exploration workflows are well covered.

    Maintenance

    ActivityActive
    ResponsivenessResponsive