Skip to main content
Glama
Sign In
treasure-data

Treasure Data MCP Server

Official
by treasure-data
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Treasure Data MCP Server

No user-submitted related servers found.

    Related Servers

    • Igloo MCP

      Evan-Kim2028
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with Snowflake databases through SQL queries, table previews, and metadata operations. Features built-in safety checks that block destructive operations and intelligent error handling optimized for AI workflows.
      30 PyPI
      1
      MIT

    • Spark SQL MCP Server

      Manju-droid
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to execute read-only SQL against Spark, Hive, and HiveServer2-compatible clusters, discover databases and table schemas, and connect using multiple authentication modes.
      MIT
    • CrateDB MCP Server by crate

      CrateDB MCP Serverofficial

      crate
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants to CrateDB clusters to enable natural-language Text-to-SQL, data analysis, and documentation retrieval. It allows users to manage database operations, troubleshoot cluster issues, and query information through conversational prompts.
      66 PyPI
      7
      Apache 2.0

    • CockroachDB MCP Server

      bpamiri
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to query and interact with CockroachDB clusters through natural language, supporting schema discovery, CRUD operations, transactions, cluster monitoring, and data export with configurable safety controls.
      30
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools target a distinct resource+action pair (list_databases vs list_tables vs describe_table; query vs execute is cleanly split by read-only vs write). The only real confusion candidates are retry_session vs retry_attempt and parent_segment_sql vs segment_sql, but the descriptions explicitly differentiate the scope (session vs attempt, parent vs filtered) so an agent can still choose correctly.

    Naming Consistency4/5

    The large majority of tools follow a verb_noun convention (list_*, get_*, retry_*, kill_attempt, describe_table, use_database). A handful deviate: bare verbs 'query' and 'execute', the noun-first getter 'current_database' (which pairs awkwardly with 'use_database'), and noun-first 'parent_segment_sql'/'segment_sql'. Minor inconsistencies, not enough to break predictability.

    Tool Count3/5

    23 tools is on the heavy side and reflects three loosely bundled products in one server: SQL/database access, experimental CDP segment APIs, and workflow/session/attempt/task inspection. Each tool does earn its place, but the workflow-debugging chain (list_sessions → get_session_attempts → get_attempt_tasks → get_task_logs) plus the experimental tag suggests the surface could be split or trimmed.

    Completeness3/5

    Read and write SQL, context switching, and deep workflow introspection are well covered, but there are noticeable gaps: no create/drop/alter table or database operations, no way to fetch a single workflow definition or start/stop a workflow job, and CDP coverage stops at listing/reading (no segment or audience creation). These are recoverable via query/execute for some cases but leave the workflow lifecycle one-sided.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources