Skip to main content
Glama

Related Servers

Alternatives to anydb-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that exposes PostgreSQL/MySQL/SQLite/MongoDB databases to AI agents, converting natural language questions into SQL queries with configurable LLM providers and safe read-only operations.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      A dead-simple, self-hosted MCP server for querying your databases with AI agents.
      95 PyPI
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP-Server from your Database optimized for LLMs and AI-Agents. Supports PostgreSQL, MySQL, ClickHouse, Snowflake, MSSQL, BigQuery, Oracle Database, SQLite, ElasticSearch, DuckDB
      547
      Apache 2.0
    • F
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that exposes relational databases (PostgreSQL/MySQL) to AI agents with natural language to SQL query support.
      19
      -
    • A
      license
      A
      quality
      A
      maintenance
      One config, one CLI that turns your databases (Postgres, MySQL, SQLite, MongoDB) into MCP servers for Claude, GPT, Cursor, and any MCP-compatible agent.
      3
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      An MCP server that gives AI agents access to configured databases (PostgreSQL, MySQL, Redshift, SQL Server) with SSH/AWS SSM tunnels, pluggable secret providers, and strict per-instance isolation.
      10
      56 npm
      MIT

    TDQS

    A4.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a clearly distinct aspect: db_query executes statements, db_explain plans without executing, db_schema introspects structure, db_list lists connection profiles, and db_health reports server status. The descriptions explicitly differentiate execution vs planning vs introspection vs connection listing vs health, so an agent can easily select the right tool.

    Naming Consistency5/5

    All five tools share a uniform db_ prefix and snake_case style, making the naming predictable and easy to scan. Although the second component is sometimes a verb (query, list, explain) and sometimes a noun (schema, health), the overall convention is consistent and unambiguous.

    Tool Count5/5

    Five tools is a well-scoped set for a multi-database MCP server. Each tool has a distinct, non-redundant role, and no obvious gaps or bloat exist within the stated scope of querying, schema inspection, planning, and health checking.

    Completeness5/5

    The surface covers the full lifecycle for database interaction: discovering connections (db_list), understanding structure (db_schema), executing read/write statements (db_query), safely planning (db_explain), and health/status (db_health). It handles multiple database types and includes safeguards, leaving no significant missing operations for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues