singlestore-mcp-server
Related Servers
Alternatives to singlestore-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides a lightweight MySQL database interface via stdio, enabling query execution, data manipulation, schema inspection, and connection testing using FastMCP tools.3MIT
- AlicenseAqualityAmaintenanceEnables Oracle Database schema introspection and SQL execution over stdio, letting MCP hosts list tables, describe columns, and run SQL—read-only by default with opt-in writes.322 npmMIT
- AlicenseCqualityCmaintenanceEnables executing SQL queries, managing databases, and switching between multiple project environments via MCP, without requiring a local MySQL client.14371 npm1MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to interact with a 达梦 DM8 database over stdio, providing read-only queries, schema exploration, and optional gated write/DDL operations with strict safety checks.938 npmApache 2.0
- AlicenseAqualityCmaintenanceEnables MCP clients such as Codex to safely inspect a MySQL database over stdio by listing tables, describing schemas and indexes, and running only validated single read-only SELECT/CTE queries plus JSON EXPLAIN plans. Queries execute inside read-only transactions with strict AST-based rejection of writes, multi-statements, and other risky operations, and results come back as structured JSON.631 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables SQL query execution and database structure browsing via MCP tools and resources.MIT
TDQS
Scored across 13 tools
Each tool targets a distinct resource or action, with clear separation between pipeline lifecycle, SQL execution, and schema introspection. Minor overlap exists between list_pipelines and pipeline_status, and run_sql can technically execute pipeline statements, but the descriptions clearly steer agents toward the dedicated tools.
Most tools follow a predictable verb_noun pattern such as create_pipeline, drop_pipeline, list_tables, and describe_table. The main deviation is pipeline_status, which would fit better as get_pipeline_status for consistency with get_pipeline_ddl.
Thirteen tools is a well-scoped size for this server's purpose. Each tool serves a clear need, covering pipeline lifecycle, query execution, and database/table introspection without unnecessary duplication.
The pipeline domain is thoroughly covered with create, alter, drop, start, stop, test, status, list, and DDL retrieval. The addition of run_sql, list_databases, list_tables, and describe_table provides a complete practical surface for working with SingleStore.