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.
      17 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.
      692 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      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
      2,699 npm
      MIT

    TDQS

    B3.4/5.0

    Scored across 32 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions, especially the table, trigger, procedure, function, package, and query-analysis families. There is some overlap among meta/introspection tools such as get-server-info vs list-available-tools, and between list-triggers, get-table-triggers, and describe-trigger, but descriptions generally make the intended use clear.

    Naming Consistency4/5

    Most tool names follow a predictable kebab-case verb_noun pattern such as list-tables, describe-table, get-table-indexes, and execute-query. The main deviations are subscribe_to_event and unsubscribe_from_event using snake_case, plus a few noun-only names like echo, but the overall convention remains readable and mostly consistent.

    Tool Count2/5

    With 32 tools, the server is well above the typical well-scoped range and includes several niche or overlapping meta tools such as list-available-tools, get-server-info, system-health-check, and batch variants. The breadth reflects a comprehensive Firebird surface, but the count feels heavy rather than tightly curated.

    Completeness4/5

    Core Firebird workflows are well covered: tables, schemas, data access, indexes, constraints, triggers, procedures, functions, packages, query execution, plans, performance analysis, events, and database/server metadata. Some object categories such as views, generators/sequences, and privileges lack dedicated list/describe tools, though agents can query system tables via execute-query as a workaround.

    Maintenance

    ActivityActive
    ResponsivenessUsually handled