Skip to main content
Glama
LostInBrittany

RAGmonsters Custom PostgreSQL MCP Server

by LostInBrittany
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to RAGmonsters Custom PostgreSQL MCP Server

No user-submitted related servers found.

    Related Servers

    • scopedb-mcp

      xieweicong
      A
      license
      Not graded
      quality
      D
      maintenance
      Config-driven MCP server that gives AI scoped, auditable database access without exposing the entire database.
      12 npm
      6
      MIT

    • mcp-crewai-giulia-ai

      wganalytics
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server enabling text-to-SQL on PostgreSQL databases using a CrewAI multi-agent system. It generates and executes read-only SQL queries from natural language, with security layers against prompt injection.
      MIT

    • Generic SQL MCP Server

      Ayushedunext
      F
      license
      Not graded
      quality
      B
      maintenance
      A configurable, database-agnostic MCP server that enables LLMs to safely interact with SQL databases through read-only operations and schema inspection.
      -

    • mcp-ohmy-sql

      MacHu-GWU
      -
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that bridges AI assistants with SQL databases, enabling natural language querying across multiple database types with built-in optimization and security.
      3
      -

    • sqldb-mcp-server

      akrym1582
      A
      license
      A
      quality
      A
      maintenance
      A read-only MCP server that exposes SQL database access to LLMs, supporting multiple database types, compact columnar results, pagination, and file export.
      7
      8 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

    B3.2/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools have distinct purposes, but 'getMonsterByHabitat' and 'getMonsters' could cause confusion since both retrieve monsters with filtering capabilities. The descriptions clarify that 'getMonsterByHabitat' is for exact habitat matching while 'getMonsters' offers broader filtering, but agents might still misselect between them.

    Naming Consistency3/5

    The naming is mixed with inconsistent patterns: 'add' uses a generic verb, 'getHabitats' and 'getMonsters' follow a verb_noun plural pattern, while 'getMonsterByHabitat', 'getMonsterById', and 'getMonsterByName' use a verb_noun_preposition format. This creates readability but lacks uniformity across all tools.

    Tool Count4/5

    With 6 tools, the count is reasonable for a PostgreSQL-based monster database server. It covers core operations like adding data and querying monsters in various ways, though it might benefit from additional tools for updates or deletions to be fully scoped.

    Completeness3/5

    The tool set covers querying and adding data well, but there are notable gaps for a database server: no update or delete tools for monsters or habitats, and no tool for creating habitats. This limits full lifecycle management and could cause agent failures in more complex workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources