Skip to main content
Glama
aradhyas8

QueryIO

by aradhyas8
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to QueryIO

No user-submitted related servers found.

    Related Servers

    • pg-mcp

      rakesh-ridecell
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to safely explore PostgreSQL schemas, inspect sample rows, draft queries, and read EXPLAIN plans through a read-only enforced interface for MCP clients.
      MIT

    • Supabase Read-Only MCP Server

      rubenyh
      F
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to safely inspect and query an explicitly allowlisted subset of a Postgres database through four read-only tools: a readiness check, table listing, column description, and typed row selection with filters, ordering, and paging. It runs over stdio for local clients or Streamable HTTP for separately managed ones, with bound parameters, bounded reads, and read-only transactions.
      4
      -

    • SQL MCP Server

      Kenza-21
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables LLM agents to explore a Postgres database and answer questions by running safe, read-only SQL queries through MCP tools.
      -

    • PG Connection Pool Query

      duylongpro99
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to run SQL queries against PostgreSQL databases through MCP with connection pooling, tenant isolation, and read-only guardrails. Supports introspection of schemas, tables, and columns.
      -

    • mcp-postgres

      4l3x31s
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to inspect PostgreSQL schemas, run read-only queries and explain plans, and, when explicitly permitted, execute writes and DDL on a per-project database with layered safety controls.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.1/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: query runs arbitrary SQL, list_tables enumerates tables, describe_tables returns schema/statistics, and inspect_row fetches a single row plus its FK neighborhood. There is no overlap that would cause misselection.

    Naming Consistency4/5

    list_tables, describe_tables, and inspect_row follow a consistent verb_noun pattern, while query is a bare verb/noun that breaks the pattern slightly. Still predictable and readable overall.

    Tool Count5/5

    Four tools is well-scoped for a read-only PostgreSQL exploration server; each tool covers a distinct layer (raw SQL, table listing, schema detail, row+FK inspection) and earns its place.

    Completeness4/5

    For an intentionally read-only server, the surface covers listing, schema description, querying, and row/relationship inspection well. Write operations and connection/health introspection are absent, but that appears to be by design rather than a functional gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources