Skip to main content
Glama
chanonwankaew-ui

Zynx Supabase MCP Server

by chanonwankaew-ui
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Zynx Supabase MCP Server

No user-submitted related servers found.

    Related Servers

    • Supabase MCP Server

      elsheppo
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes your application's resources and tools as an MCP server using Supabase Auth, Postgres, and Row Level Security, allowing authorized users to connect via compatible MCP clients.
      255 npm
      2
      MIT

    • MCP Server TypeScript

      ichetanmittal
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      A production-ready TypeScript MCP server providing basic tools (add, echo, timestamp), resources (server info, greetings, data access), and prompt templates (analyze, code-review, summarize). Serves as a foundation for building custom MCP servers with extensible architecture.
      205 npm
      -

    • SupaMCPBuilder

      vivek100
      A
      license
      Not graded
      quality
      D
      maintenance
      A runtime-configurable MCP server for Supabase databases that enables dynamic tool creation through JSON configuration. Build custom database operations (select, insert, update, delete) without writing code, with built-in authentication and template support.
      5 npm
      11
      MIT

    • mcp-suite

      mcp-nexus
      A
      license
      Not graded
      quality
      D
      maintenance
      A production-grade TypeScript MCP server that provides AI agents with structured access to real-world data across financial markets, Web3/DeFi, developer tools, and healthcare domains. It features built-in authentication, domain isolation, caching, and rate limiting for reliable API integrations.
      5 npm
      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.5/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action pair: health, table listing, generic query, memory search, memory write, project create, file listing, and file read. No two tools perform the same operation on the same resource.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (get_, list_, query_, search_, add_, create_, read_). The style is uniform and predictable.

    Tool Count5/5

    With 8 tools, the server covers its core capabilities without bloat. It is within the ideal 3-15 range and each tool serves a clear purpose.

    Completeness2/5

    The tool surface is notably incomplete: memory supports add and search but no update or delete; projects support create but no retrieval, update, or delete; workspace files support list and read but no write. These are significant gaps for a server that claims to support orchestration, memory, and automation.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources