mcpolyglot
Related Servers
Alternatives to mcpolyglot
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceZero-config MCP server that empowers AI agents to safely query SQL and NoSQL databases like PostgreSQL, MySQL, SQLite, MongoDB, and Redis.51,639 npm1MIT
- AlicenseNot gradedqualityAmaintenanceA dead-simple, self-hosted MCP server for querying your databases with AI agents.61 PyPI2MIT
- AlicenseNot gradedqualityDmaintenanceA production-ready MCP server for PostgreSQL — built for Claude Desktop, Claude Code, and any MCP-compatible AI agent.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP-Server from your Database optimized for LLMs and AI-Agents. Supports PostgreSQL, MySQL, ClickHouse, Snowflake, MSSQL, BigQuery, Oracle Database, SQLite, ElasticSearch, DuckDB548Apache 2.0
- AlicenseAqualityDmaintenanceTurn any data source into an MCP server in 5 minutes. Build knowledge bases that AI assistants like Claude and Cursor can query directly.222 npm22MIT
- FlicenseNot gradedqualityBmaintenanceAn 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
Scored across 3 tools
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.
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.
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.
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.