Skip to main content
Glama

Related Servers

Alternatives to Regent MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects Supabase projects to AI assistants, enabling them to manage database tables, execute SQL queries, and deploy Edge Functions through natural language. It provides a comprehensive suite of tools for project administration, including logs access, documentation search, and environment configuration.
      Apache 2.0
    • 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.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI assistants to Supabase projects, enabling them to manage tables, query data, deploy Edge Functions, handle migrations, and access project resources through natural language commands.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLM agents to read and modify company data from Notion and Supabase, with human-in-the-loop approval for all write and delete operations.
      4 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to access and manage Supabase projects through the Model Context Protocol, supporting database operations, edge functions, storage, and documentation search. It provides a complete toolset for SQL execution, migration management, and real-time project debugging.
      -
    • A
      license
      C
      quality
      B
      maintenance
      Enables comprehensive management of self-hosted Supabase instances on Coolify, including database migrations, edge functions deployment, storage management, auth configuration, and full application lifecycle control through AI agents.
      56
      5 npm
      3
      MIT

    TDQS

    A3.5/5.0

    Scored across 28 tools

    Disambiguation4/5

    Most tools are clearly scoped to a single resource and action, and the descriptions clarify boundaries. The main risk is among the seven analytics tools, but their differing timeframes and aggregation levels are distinct enough to avoid serious misselection.

    Naming Consistency5/5

    Tool names consistently follow a verb_noun snake_case pattern: list_, get_, create_, update_, delete_, set_, add_, send_, and reply_. Even mixed pluralization like list_job_applications vs get_consultation_request does not undermine the clear convention.

    Tool Count2/5

    At 28 tools, the server exceeds the 25-tool threshold and feels heavy even though it spans several domains. The tools are individually useful, but the overall surface is large enough that an agent may struggle to scan and choose efficiently.

    Completeness4/5

    Content, job postings, consultation requests, newsletters, and analytics are largely well covered with sensible lifecycle operations. Minor gaps exist, such as no single get_job_posting tool and no subscriber management beyond listing and sending, but these can be worked around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues