sql-mcp
Related Servers
Alternatives to sql-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables AI assistants to connect to SQL Server databases and execute arbitrary SQL operations, including queries, updates, table management, and script execution, through the Model Context Protocol.7-
- AlicenseBqualityCmaintenanceEnables AI assistants to connect to Microsoft SQL Server for schema discovery, querying, stored procedures, DDL, performance diagnostics, and developer utilities with configurable security modes.3550 npmMIT
- AlicenseBqualityCmaintenanceEnables VS Code Copilot Chat and custom agents to perform MongoDB queries, writes, transactions, schema discovery, index and collection management, and administrative commands across multiple secure connection profiles without using mongosh or PowerShell.28MIT
- AlicenseNot gradedqualityDmaintenanceEnables Cursor AI to interact with SQL Server databases, including querying, schema exploration, report generation, and chart creation.6 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to discover SQL Server connections from VS Code or Antigravity IDE, inspect databases, schemas, tables, views, and functions, and execute read-only T-SQL queries over stdio across multiple connections.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Microsoft SQL Server databases through a standardized interface. Supports executing SQL queries, browsing database schemas, and viewing table data with flexible authentication options for both local and Azure SQL databases.5MIT
TDQS
Scored across 30 tools
Each tool targets a distinct resource+action: connection management, query execution (execute_sql vs execute_procedure clearly separated), transaction control, metadata inspection, Agent jobs, and sessions. A few pairs have subtle overlap (list_jobs vs list_running_jobs, get_job vs get_job_history, update_job vs update_job_step), but descriptions sharpen the boundaries well.
Almost entirely consistent verb_noun snake_case (list_connections, add_connection, create_job, delete_job_step, get_job_history, kill_session). The only deviation is transaction_status, which is noun-first, a minor blip in an otherwise predictable scheme.
30 tools is heavy; the Agent-job surface alone consumes 14 tools (CRUD for jobs, steps, schedules, history, running). Each tool does something distinct, but the set is large enough that scope feels sprawling rather than tightly earned.
Broad and well-rounded: connection CRUD, arbitrary T-SQL, procedure execution, full transaction lifecycle, metadata (databases/objects/describe_table/definitions), full Agent job lifecycle, and session monitoring. Minor gaps exist (no dedicated query-plan/EXPLAIN, no user/permission or index-management helpers), but execute_sql can cover most of these.