Skip to main content
Glama
Sign In
Qora

Qora

by suveshmoza
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Qora

Talk to your data. Get clear answers, insights, and analysis.

Qora lets AI assistants like Cursor and Claude safely explore your database and answer questions about your data in plain English.

Ask things like:

"How many orders did we receive last month?"

"Which products are selling the most?"

"Show me the tables related to customers."

Qora looks up the answers directly from your database and gives them back to your AI assistant.

Qora is read-only by design. It can inspect and query your data, but it cannot insert, update, or delete anything.

M8ven Score

How it works

flowchart LR
  You["You ask a question"] --> AI["AI assistant<br/>(Cursor, Claude, …)"]
  AI -->|"uses Qora tools"| Qora["Qora"]
  Qora -->|"explore & read-only queries"| DB[("Your database")]
  DB -->|"rows & schema info"| Qora
  Qora -->|"safe results"| AI
  AI -->|"clear answer"| You

  1. You ask something.

  2. Your AI assistant calls Qora.

  3. Qora looks up schemas/tables or runs a read-only query.

  4. Results go back to the assistant, which answers you.

Related MCP server: MCPBridge

What Qora does

Qora gives your AI assistant safe, read-only access to the database.

  • Discover schemas and tables - so the assistant knows what’s available

  • Describe table structure - columns, types, and nullability

  • Run read-only SQL - the assistant writes the query; Qora validates and executes it

  • Return results safely - capped row counts, no writes or schema changes

Read-only by design

  1. Only read-style queries are allowed

  2. Connect with a read-only database user

  3. Result size is capped

  4. HTTP access can be limited to specific hosts

Tools

Tool

What it does

list_schemas

See the main areas of your data

list_tables

See what tables exist

describe_table

Understand what's inside a table

run_query

Run a validated read-only SELECT

Docs

  • Setup - install, env, MCP clients, HTTP, Docker

  • Contributing - Dev Container, scripts, PR checklist

Available Tools

4 tools
describe_tableDescribe tableA
Read-only

Get column names, data types, and nullability for a specific table. Call this before querying a table you haven't seen the schema for.

Inputs: schema (required), table_name (required).

list_schemasList schemasA
Read-only

List database schemas the agent can see (system schemas excluded). Call this first to discover which schemas exist, then list_tables / describe_table.

Inputs: no named parameters.

list_tablesList tablesA
Read-only

List tables and views the agent can query. Optionally filter by schema. Always call this (or describe_table) before writing a query against an unfamiliar table.

Inputs: schema.

run_queryRun queryA
Read-only

Run a read-only SQL SELECT against Postgres. Only SELECT is permitted — writes, DDL, and multi-statement queries are rejected. Results capped at 1000 rows and returned as JSON ({ columns, rowCount, rows }). Prefer GROUP BY / aggregation over raw dumps. Always qualify table names with schema, e.g. SELECT * FROM analytics.orders. Discover schemas/tables via list_schemas, list_tables, and describe_table first.

Inputs: sql (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: discovering schemas, listing tables, describing table schemas, and executing queries. No overlap or ambiguity.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (list_schemas, list_tables, describe_table, run_query), making the naming predictable and clean.

    Tool Count5/5

    With 4 tools, the set is well-scoped for a read-only database exploration and querying server. Each tool is necessary and sufficient for the core workflow.

    Completeness5/5

    The surface covers the full discovery-to-query lifecycle: schema discovery, table listing, schema introspection, and read-only query execution. No essential operations are missing for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    • MCP Guide Schema Query

      BaoNgoThien18
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI tools to understand a database, inspect schema, and run safe SELECT queries with SQL guardrails, plus optional codebase reading.
      MIT

    • MCPBridge

      manulthanura
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants to PostgreSQL databases with production-grade safety features including query validation, guarded writes, rate limiting, and audit logging.
      3
      MIT

    • 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

    • 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