Skip to main content
Glama
kosminus

querywise-mcp

by kosminus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to querywise-mcp

No user-submitted related servers found.

    Related Servers

    • Datum

      malharinamdar
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables natural-language querying of SQLite databases through a governed semantic layer, with citations and typed abstention for PII or uncertified data.
      -

    • db-connector

      adlkt
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query business databases directly via natural language, with enforced read-only access and secure query limits. Supports SQLite and PostgreSQL, and works with any OpenAI-compatible model.
      0
      ISC
    • NLQueries by nlqueries

      NLQueriesofficial

      nlqueries
      F
      license
      A
      quality
      A
      maintenance
      Natural language to SQL engine with multi-connector support (PostgreSQL, MySQL, Snowflake, BigQuery, DuckDB), document QA, semantic caching, and self-hosted MCP server.
      9
      150 PyPI
      5
      -

    • MCP-DB-Server

      sujalsamkaria0066
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language querying of SQL databases with robust safety guarantees including read-only enforcement, AST validation, and row caps.
      -

    • warehouse-mcp

      usamaattia
      A
      license
      Not graded
      quality
      C
      maintenance
      Lets an AI assistant explore and query Postgres, DuckDB, or Snowflake with read-only SQL, table and schema discovery, sampling, and explainable guardrails.
      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.2/5.0

    Scored across 25 tools

    Disambiguation5/5

    Each tool targets a distinct resource or pipeline stage: connection setup, schema introspection, context assembly, SQL generation, execution, and end-to-end asking are clearly separated. The add/list/delete groups for glossary, metrics, knowledge, and sample queries are also unambiguous, with descriptions cross-referencing alternatives.

    Naming Consistency4/5

    Most tools follow a predictable verb_noun pattern (list_*, add_*, delete_*, create_connection). Minor deviations like 'ask', 'query_history', and 'get_semantic_context' break the pattern slightly but remain understandable.

    Tool Count3/5

    25 tools is on the heavy side for a single server, even though the domain spans connection management, SQL querying, and semantic metadata CRUD. Each tool appears justified, but the set could plausibly be split into configuration and querying sub-servers.

    Completeness4/5

    The core lifecycle is well covered: connections can be created/tested/introspected/deleted, SQL can be generated/run/reviewed, and most semantic resources have add/list/delete. Notable missing operations are deleting sample queries and listing/deleting dictionary entries, leaving small management gaps.

    Maintenance

    ActivityInactive
    ResponsivenessResponsive

    Resources