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
      C
      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
      39 npm
      2
      MIT

    • Oracle DB MCP

      muazam99
      F
      license
      Not graded
      quality
      D
      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.
      107 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
      16 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.8/5.0

    Scored across 49 tools

    Disambiguation3/5

    Many tools have clearly distinct purposes, and descriptions cross-reference alternatives (e.g., explainQuery vs analyzePlan). However, dense clusters around query analysis (executeQuery/timedQuery/benchmarkQuery/validateQuery/queryLint), column profiling (columnStats/columnDistribution/columnHistogram/nullRatio), and index auditing (fkIndexCoverage/redundantIndexes/unusedIndexes/indexStats) create real overlap that can cause misselection.

    Naming Consistency3/5

    All names are camelCase and readable, but the convention mixes verb-first actions (listTables, describeTable, findJoinPaths) with noun-only analysis results (columnStats, schemaGraph, indexStats). This is not a consistent verb_noun pattern, though it remains understandable.

    Tool Count2/5

    49 tools is far above the 3–15 ideal and exceeds the 25-tool threshold for being too many. The domain is broad, but several overlapping clusters could likely be consolidated into fewer multi-purpose tools.

    Completeness4/5

    The read-only introspection surface is extremely thorough: connections, schemas, tables/views, routines, triggers, sequences, columns, stats, indexes, joins, query parsing/validation/execution/plans/lineage, and usage-catalog discovery. Minor gaps exist (e.g., no standalone listTriggers or listViews, relying on listTables/searchObjects), but agents can work around them.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources