Skip to main content
Glama
igorolv

jdbc-mcp-server

by igorolv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to jdbc-mcp-server

No user-submitted related servers found.

    Related Servers

    • dbridge-mcp

      ugurcl
      A
      license
      A
      quality
      A
      maintenance
      Read-only MCP server that lets AI agents safely query SQLite, PostgreSQL, and MySQL/MariaDB. Enforces read-only transactions with column masking, row caps, query timeouts, EXPLAIN-based cost rejection, and rate limiting.
      7
      24 npm
      1
      MIT

    • Oracle DB MCP

      muazam99
      F
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server that lets coding AI agents inspect Oracle Database schema through live metadata.
      -

    • mcp-db-connect

      phatngoit
      A
      license
      Not graded
      quality
      A
      maintenance
      Universal MCP server for readonly-first access to Oracle, SQL Server, PostgreSQL, MySQL/MariaDB, SQLite, MongoDB, and Qdrant vector search.
      41 npm
      1
      MIT

    • sql-explorer-mcp

      govern-agents
      A
      license
      Not graded
      quality
      F
      maintenance
      Read-only MCP server for SQL databases (SQL Server, Postgres, SQLite) with multi-server support and three-layer safety using AST validation and linting.
      MIT

    • mcp-multi-db

      mahAnuj
      A
      license
      A
      quality
      B
      maintenance
      Read-only MCP server for querying PostgreSQL, MySQL, and SQLite from AI agents — multi-database, safe by default.
      4
      17 npm
      1
      ISC
    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

    A3.9/5.0

    Scored across 49 tools

    Disambiguation3/5

    The tool set is generally well-separated, but there are several close clusters: query inspect/validate/lint/lineage, explain/analyze plan, columnStats/distribution/histogram, and redundant/unused/FK index tools. Descriptions and cross-references mostly disambiguate them, but with 49 tools an agent can still plausibly select the wrong member of such a cluster.

    Naming Consistency4/5

    Names are uniformly lowerCamelCase and mostly follow a readable verb+object pattern like listTables, getViewDefinition, and executeQuery. Some noun-first names like schemaGraph, columnStats, and tableContext form a consistent secondary style rather than chaotic mixing, so the naming remains predictable.

    Tool Count2/5

    49 tools far exceeds the 25-tool threshold for a well-scoped server. Many tools are highly granular variants—three column-stat tools, several query-analysis tools, and multiple index-audit tools—that could reasonably be consolidated, making the overall surface heavy for an agent.

    Completeness4/5

    For a read-only JDBC introspection and query-analysis server, coverage is very thorough: object discovery, metadata, sampling, relationships, query execution, plan diagnosis, index auditing, and usage-catalog lifecycle are all represented with few dead ends. Minor gaps such as table DDL generation or bulk cross-schema listing are workable via existing tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources