Skip to main content
Glama
CelpAI

celp-mcp

Official
by CelpAI

Related Servers

Alternatives to celp-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables natural language querying of SQL databases and REST APIs through the MCP protocol, grounded in a semantic layer.
      1,395 npm
      1
      AGPL 3.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP (Model Context Protocol) server that exposes natural language to SQL functionality, allowing any MCP-compatible client to convert plain English questions into SQL queries for database interaction using AI.
      3
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A database-agnostic MCP server that enables natural language queries to your database through Claude or Copilot, automatically writing and executing SQL.
      8
      4 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enables natural-language SQL queries across multiple databases (ClickHouse, Teradata, PostgreSQL, MySQL, SQL Server, DB2, Oracle, MongoDB) with dialect-correct SQL generation, PII masking, and security-by-construction controls.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for SQL analytics on DuckDB and MotherDuck databases, enabling AI assistants and IDEs to query data via natural language.
      1
      MIT
    • F
      license
      Not graded
      quality
      F
      maintenance
      A production-ready MCP server that transforms natural language into safe, executable SQL queries with multi-database support and intelligent schema analysis.
      1
      -

    TDQS

    B3.3/5.0

    Scored across 4 tools

    Disambiguation4/5

    The two metadata tools (get-index-map, get-schema) are clearly distinct. The two query tools (query-database, query-database-turbo) serve different complexity levels, but their overlapping purpose could cause confusion if the agent misjudges the query difficulty.

    Naming Consistency5/5

    All tool names follow a consistent hyphenated lowercase pattern: get for metadata retrieval and query for querying, with a suffix for the turbo variant. The naming is uniform and predictable.

    Tool Count5/5

    With 4 tools covering metadata retrieval and two query modes, the count is well-scoped for a database server. No unnecessary tools, and each serves a distinct purpose.

    Completeness3/5

    The tool surface covers schema/index inspection and both simple and complex querying. However, it lacks write operations (insert, update, delete) and explicit table listing, which are notable gaps for a comprehensive database server.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues