Skip to main content
Glama
rubenyh

Supabase Read-Only MCP Server

by rubenyh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Supabase Read-Only MCP Server

No user-submitted related servers found.

    Related Servers

    • slcg

      aadhyathmik
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a read-only PostgreSQL MCP server with schema introspection. Enforces least-privilege database roles to prevent any writes, even from malicious SQL.
      MIT

    • safe-postgres-mcp

      lucasoresi
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server for safe read-only PostgreSQL exploration and querying, enforced by three independent layers: startup privilege audit, lexical guard, and read-only transactions. Offers tools for querying, table listing, schema description, relationship mapping, and query explanation.
      18 npm
      MIT

    • mcp-devdb

      aminyx
      A
      license
      Not graded
      quality
      B
      maintenance
      A safe, read-only MCP server for local development databases (PostgreSQL and SQLite) that provides guarded introspection tools like schema listing, sample rows, and explain plans with column masking and query budgets.
      MIT

    • postgres-mcp

      gabriel-herencia
      A
      license
      A
      quality
      C
      maintenance
      A self-hostable PostgreSQL MCP server for exploring database schemas and running guarded read/write queries with selectable access modes (readonly, readwrite, admin), plus a dry-run confirm workflow for safety.
      14
      1
      MIT

    • postgres-mcp-server

      bysonte
      A
      license
      A
      quality
      C
      maintenance
      Local MCP server for safe querying and inspecting PostgreSQL databases, with write and maintenance operations disabled by default.
      8
      17 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.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: health_check for server/database status, list_allowed_tables for table enumeration, describe_table for schema metadata, and select_rows for data retrieval. There is no overlap or confusion between these roles.

    Naming Consistency4/5

    All tools use snake_case, which is consistent. However, health_check breaks the verb_noun pattern followed by list_allowed_tables, describe_table, and select_rows, creating a minor deviation.

    Tool Count5/5

    Four tools are well-scoped for a focused read-only server. Each tool earns its place, covering health, table listing, schema description, and row selection without redundancy.

    Completeness4/5

    The surface covers health checks, table discovery, schema metadata, and data selection, which is nearly complete for read-only access. Minor gaps like explicit schema listing or relationship introspection exist but are not critical.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources