Skip to main content
Glama
cosmosluna

Hermes Supabase MCP

by cosmosluna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Hermes Supabase MCP

No user-submitted related servers found.

    Related Servers

    • Supabase MCP Server

      JiayuuWang
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides secure access to Supabase databases via PostgREST API and management tools for projects, schemas, branches, logs, and code generation.
      MIT

    • mcp-supabase

      GabsPereiraDev
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Supabase databases, including listing tables, querying, inserting, updating, deleting records, and executing RPC functions.
      53 npm
      MIT

    • Supabase MCP Server

      dedalus-labs
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables secure interaction with Supabase databases via the PostgREST API, supporting full CRUD operations and stored procedure calls. It utilizes the Dedalus MCP framework to provide encrypted credential handling and just-in-time token exchange.
      4
      MIT

    • project-supabase-api

      andrewsetness
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to safely interact with Supabase through read-only and gated-write tools, with bounded queries, allowlists, and explicit project targeting.
      -

    • Supabase MCP Server

      addity3
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to interact with Supabase databases through standardized CRUD operations including querying, inserting, updating, and deleting records with support for filtering, pagination, and column selection.
      -
    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.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool maps to a distinct CRUD operation or health check, with insert vs. upsert boundaries clearly explained (insert fails on conflict, upsert merges with conflict keys). No overlapping purposes that would cause misselection.

    Naming Consistency5/5

    All tool names follow the same supabase_<operation> snake_case pattern. 'health' is the only non-verb label, but it remains a clear operation name within the same prefix convention.

    Tool Count5/5

    Six tools are well-scoped for safe table-row operations plus a connectivity check. Each tool earns its place without redundancy or filler.

    Completeness5/5

    The set provides full CRUD lifecycle coverage (select, insert, upsert, update, delete) plus a health check for the stated allowed-table domain. No obvious dead ends exist for safe PostgREST-based row operations, though schema introspection or RPC is outside the apparent scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources