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
      22 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
      371 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      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
      38 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
      31 npm
      MIT

    TDQS

    A4.2/5.0

    Scored across 13 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues