Skip to main content
Glama
nla-agent

mcp-backend

by nla-agent
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-backend

No user-submitted related servers found.

    Related Servers

    • Datris MCP Server

      datris
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server with 32 tools for ETL ingestion, AI-generated data quality rules, AI transformations, vector search, and natural-language SQL. Works across Postgres, MongoDB, Kafka, S3/MinIO, HashiCorp Vault, and five vector stores (Qdrant, Weaviate, Milvus, Chroma, pgvector).
      12
      AGPL 3.0

    • mcp-database

      justpoypoy
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for connecting to databases (PostgreSQL, MySQL, SQL Server, Redis) enabling SQL queries, table exploration, and Redis key-value operations.
      1
      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

    • @cocaxcode/database-mcp

      cocaxcode
      A
      license
      A
      quality
      C
      maintenance
      A database MCP server providing 33 tools across PostgreSQL, MySQL, and SQLite, with connection groups, rollback, dump/restore, and schema auto-discovery via natural language.
      34
      133 npm
      2
      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

    B3.4/5.0

    Scored across 31 tools

    Disambiguation4/5

    Most tools have distinct purposes, but there is some overlap between execute_sql, query_db, and execute_rls_sql, as well as between upload_file and bulk_upload_files. However, descriptions clarify the differences, making ambiguity low overall.

    Naming Consistency4/5

    The majority of tools follow a verb_noun pattern (e.g., bootstrap_iceberg, delete_file). A few, like active_queries and column_stats, deviate slightly, but the overall convention is consistent and predictable.

    Tool Count4/5

    With 31 tools, the count is on the higher side but still reasonable given the broad scope covering database operations, storage, Iceberg, seeding, and RPC. Each tool serves a specific purpose, and the number is appropriate for the server's domain.

    Completeness4/5

    The tool set covers most essential operations for a backend/database server: SQL execution, storage management, Iceberg integration, seeding, and RPC calls. Missing are explicit schema modification tools, but those can be done via execute_sql. Overall, the surface is comprehensive.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources