mcp-sqlalchemy
Related Servers
Alternatives to mcp-sqlalchemy
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceProvides generic Open Database Connectivity (ODBC) to any Database Management System (DBMS) that's accessible via an ODBC Connector (Driver).12MIT
- FlicenseNot gradedqualityDmaintenanceEnables read-only exploration and querying of Microsoft SQL Server databases through a standardized interface.2-
- AlicenseNot gradedqualityCmaintenanceEnables LLMs to query ODBC-accessible databases via DSN, supporting SQL, SPARQL, and schema exploration.MIT
- AlicenseNot gradedqualityDmaintenanceEnables SQL agents to connect to any SQLAlchemy-supported database via MCP, providing read-only SQL querying, automatic table summarization, and column content search.4Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Microsoft SQL Server databases using both SQL Server and Windows Authentication. It supports flexible connection configurations, including read-only modes and encrypted communication for secure data management.3,848 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables interaction with Microsoft SQL Server by executing queries, statements, and stored procedures, as well as retrieving schema metadata through the Model Context Protocol.6 npmMIT
TDQS
Scored across 11 tools
Multiple tools have overlapping or unclear purposes, causing confusion. For example, podbc_execute_query and podbc_query_database both execute SQL queries and return results in JSONL format, making them nearly indistinguishable. Additionally, podbc_sparql_func and podbc_virtuoso_support_ai have vague descriptions that don't clearly differentiate their functions from other query tools.
The naming follows a consistent prefix pattern (podbc_) and uses snake_case throughout, which is predictable. However, there are minor deviations like podbc_spasql_query (likely a typo for SPARQL) and inconsistent verb usage (e.g., get_schemas vs. filter_table_names), but overall the structure is readable and mostly uniform.
With 11 tools, the count is reasonable for a database interaction server, covering schema exploration, table queries, and specialized functions. It's slightly on the higher side but still manageable, as each tool appears to serve a distinct technical purpose, though some redundancy exists.
The toolset covers core database operations like querying, schema retrieval, and table description, but there are notable gaps. For instance, there are no tools for data manipulation (e.g., insert, update, delete) or transaction management, which are essential for a complete SQLAlchemy-like interface. The inclusion of SPARQL and specialized functions adds niche coverage but doesn't fill these basic CRUD gaps.