Skip to main content
Glama
ishay60

mcpolyglot

Related Servers

Alternatives to mcpolyglot

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Zero-config MCP server that empowers AI agents to safely query SQL and NoSQL databases like PostgreSQL, MySQL, SQLite, MongoDB, and Redis.
      5
      1,639 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      A dead-simple, self-hosted MCP server for querying your databases with AI agents.
      61 PyPI
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A production-ready MCP server for PostgreSQL — built for Claude Desktop, Claude Code, and any MCP-compatible AI agent.
      Apache 2.0
    • 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
      548
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      Turn any data source into an MCP server in 5 minutes. Build knowledge bases that AI assistants like Claude and Cursor can query directly.
      2
      22 npm
      22
      MIT
    • 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.
      -

    TDQS

    A3.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct purpose: listing all tables, describing one specific table, and executing read-only queries. There is minor overlap in that list_tables also returns columns, but the boundary between the three is clear enough that an agent can reliably pick the right one.

    Naming Consistency4/5

    Names use a consistent snake_case verb_noun convention (describe_table, list_tables) with a uniform 'demo.' namespace prefix. demo.query is a slight deviation since it lacks a noun object, but it remains readable and clearly scoped.

    Tool Count4/5

    Three tools is on the lean side but appropriate for a deliberately read-only demo database exploration surface. Each tool earns its place without redundancy.

    Completeness4/5

    List, describe, and query cover the core read-only exploration lifecycle with no dead ends, since arbitrary queries can retrieve counts, samples, and joins. A few conveniences (e.g., a schema-wide search or sample-row helper) are absent but easily worked around via query.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues