Skip to main content
Glama
arman1o1

mcp-db-explorer

by arman1o1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-db-explorer

No user-submitted related servers found.

    Related Servers

    • PostgreSQL MCP Server

      guibracco
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI assistants to interact with PostgreSQL databases by executing SQL queries and inspecting database schemas. It provides tools for standardized database exploration and management through the Model Context Protocol.
      -

    • sqlite-mcp-server

      helmi75
      A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server that enables LLMs to safely explore and query any SQLite database via natural language. It exposes tools for listing tables, describing schemas, and executing SELECT/WITH queries with built-in safety guards like write prevention and row limits.
      MIT

    • QueryCraftMCP

      ratchanonth60
      A
      license
      Not graded
      quality
      D
      maintenance
      A flexible Model Context Protocol server that enables LLMs to interact with database systems, supporting dynamic schema discovery and query execution across PostgreSQL and SQLite backends.
      2
      MIT

    • database-mcp-server

      echatzief
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides database operations as tools for LLM-powered applications. Supports PostgreSQL, MySQL, and MongoDB databases with connection pooling and flexible result formatting.
      -
    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/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: connection, schema description, query planning, ERD generation, statistics, table listing, and query execution. There is no overlap between them.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (e.g., connect_database, list_tables, run_query). No deviations or mixed conventions.

    Tool Count5/5

    Seven tools is well-scoped for a database explorer. Each tool covers a necessary operation without being too few or too many.

    Completeness5/5

    The tool set covers the full lifecycle of database exploration: connection, listing tables, describing schemas, profiling stats, generating ERDs, explaining query plans, and executing queries. No obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources