Skip to main content
Glama
jonasliesas

singlestore-mcp-server

by jonasliesas

Related Servers

Alternatives to singlestore-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides a lightweight MySQL database interface via stdio, enabling query execution, data manipulation, schema inspection, and connection testing using FastMCP tools.
      3
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables 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.
      3
      16 npm
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      Enables executing SQL queries, managing databases, and switching between multiple project environments via MCP, without requiring a local MySQL client.
      14
      683 npm
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      9
      16 npm
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      6
      66 npm
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients to inspect and operate SQLite, PostgreSQL, MySQL/MariaDB, Oracle, SQL Server and MongoDB through 16 tools covering schema discovery, parameterized SQL reads and transactions, MongoDB document operations, and concurrent hybrid SQL/MongoDB queries. Runs locally over stdio or loopback HTTP with pooled connections, bounded concurrency, row and response limits, and read-only defaults.
      16
      MIT

    TDQS

    C2.8/5.0

    Scored across 100 tools

    Disambiguation2/5

    Many tools overlap: run_sql, query_grid, and sql_editor_query all execute SQL; query_history_advisor and query_advisor_report both give table-design advice; list_connections/connections_state and use_connection/connection_activate duplicate functions. Descriptions clarify some context, but with 100 tools an agent faces multiple unclear boundaries and near-duplicates.

    Naming Consistency3/5

    All names use snake_case, but the pattern is inconsistent: verb_noun (list_tables), noun-only (schema_explorer), prefix_noun_action (sql_editor_save_file), and singular/plural mixing (connection_* vs connections_*). Mixed conventions but still readable.

    Tool Count1/5

    100 tools is an extreme mismatch for an MCP server, far beyond the typical 3-15 range. Many app-specific tools likely overwhelm the agent and dilute focus.

    Completeness4/5

    Core SingleStore surface is well covered: SQL execution, schema listing, pipeline CRUD/start/stop/test, notebook lifecycle, query history, alerts, and connections. Minor gaps like general query cancellation, user/permission management, and backup can be worked around with run_sql, but no full admin coverage.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues