Skip to main content
Glama
0103juan

legacy-db-mcp

by 0103juan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to legacy-db-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-sql-agent

      shravyatgowda
      A
      license
      Not graded
      quality
      C
      maintenance
      Gives an LLM read-only, schema-aware SQL database access so users can ask business questions in plain English and receive the exact result set, with malformed queries returned as errors for automatic retry and correction.
      MIT

    • AI SQL Agent MCP Server

      rajmyagentit-del
      A
      license
      Not graded
      quality
      B
      maintenance
      Lets AI clients ask natural-language questions about a SQL database with production-safe guardrails, schema grounding, and read-only enforcement.
      MIT

    • pg-readonly-mcp

      MadlyFriese
      F
      license
      A
      quality
      C
      maintenance
      Enables read-only exploration of a Postgres database using natural language, with multiple safety layers to prevent any modifications.
      5
      -

    • oradb-explorer-mcp

      arun-siv
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only exploration of Oracle databases through natural language, providing schema inspection and safe bounded SQL query execution.
      -

    • mcp-db-server

      rudraraval4
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLM clients to query SQL databases via natural language with read-only, AST-validated, and capped queries, ensuring safety guarantees.
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool maps to a single, distinct step in a schema-first exploration workflow: enumerate tables, inspect one table's schema, then execute a query. There is no overlap between listing, describing, and running, and the descriptions explicitly state ordering ('Call this first', 'Call this before writing a query').

    Naming Consistency5/5

    All three tools follow a uniform snake_case verb_noun pattern (list_tables, describe_table, run_query). The verbs are precise and the noun conventions are consistent across the set.

    Tool Count5/5

    Three tools is the canonical minimal set for a read-only database: discover tables, inspect a table, query data. Each tool earns its place with no redundancy and no artificial splitting of responsibilities.

    Completeness4/5

    The surface covers the core read-only lifecycle well, and the row-limit/truncated behavior is documented. Minor gaps remain: no cross-table column search, no relationship/foreign-key mapping, and no pagination or export beyond the 200-row cap, though agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources