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.
      11 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.
      729 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
      D
      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
      3,848 npm
      MIT

    TDQS

    B3.4/5.0

    Scored across 30 tools

    Disambiguation4/5

    The parallel list/describe families for tables, triggers, procedures, functions, and packages keep most tools clearly distinct. Some overlap exists between system-health-check, get-database-info, get-server-info, and list-available-tools, but the descriptions generally differentiate their purposes well enough.

    Naming Consistency4/5

    Most tools follow a clear verb-object hyphenated pattern like list-tables, describe-table, get-table-indexes, and analyze-query-performance. The main inconsistencies are subscribe_to_event using an underscore and system-health-check not following the verb-first convention.

    Tool Count2/5

    At 30 tools, the server is overprovisioned for its apparent scope. The count is inflated by server-metadata tools like list-available-tools, get-tool-help, and get-server-info, plus batch variants that add convenience but not essential capability.

    Completeness4/5

    The toolset covers query execution, schema inspection, metadata for triggers/procedures/functions/packages, indexes, constraints, performance analysis, events, and connection health. Gaps include explicit write/DDL wrappers and metadata for objects like views and sequences, though execute-query provides a general workaround.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week