Skip to main content
Glama
HarryB05

supabase-schema-mcp

by HarryB05
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to supabase-schema-mcp

No user-submitted related servers found.

    Related Servers

    • Self-Hosted Supabase MCP

      abushadab
      F
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables interaction with self-hosted Supabase instances, allowing developers to query database schemas, manage migrations, inspect statistics, and interact with Supabase features directly from MCP-compatible development environments.
      21
      1
      -

    • PostgreSQL MCP Server

      eltonf
      A
      license
      Not graded
      quality
      D
      maintenance
      An open-source MCP server for PostgreSQL schema introspection and guarded read-only queries. It enables MCP clients to discover schemas, tables, columns, indexes, relationships, and safe queryable data from a configured PostgreSQL database.
      8 npm
      MIT

    • airis-mcp-supabase-selfhost

      agiletec-inc
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server for self-hosted Supabase with RLS-aware PostgreSQL and PostgREST layers, enabling safe database introspection, SQL queries, and PostgREST access via natural language.
      MIT

    • supabase-model-context

      andrewkorot
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for exploring and querying Supabase databases with interactive React widgets for schema browsing, table viewing, and SQL execution.
      3,783,052 npm
      1
      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

    A3.8/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool is prefixed by a distinct resource domain (schema, rls, functions, relationships, triggers) and then an action (list/get). Even functions_list vs functions_list_rpc_candidates are clearly distinguished by the 'rpc_candidates' modifier. No two tools target the same resource+action combination.

    Naming Consistency5/5

    All tools use snake_case with a consistent <domain>_<action>_<object> pattern, e.g., schema_list_tables, rls_get_policy, relationships_list_indexes. There are no mixed conventions or irregular verbs.

    Tool Count5/5

    13 tools is well-scoped for a schema introspection server, covering major Postgres object types (tables, columns, views, enums, RLS, functions, relationships, triggers) without being excessive. Each tool earns its place.

    Completeness4/5

    The server provides strong coverage of listing and detail operations for the main schema objects. Minor gaps include no explicit list-schemas tool and no full table/view DDL definitions, but these can be worked around using schema_name='all' and existing list tools.

    Resources