Skip to main content
Glama
rawtreedb

RawTree MCP Server

Official
by rawtreedb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to RawTree MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-duckdb-analyst

      nkrimmel
      A
      license
      A
      quality
      C
      maintenance
      Enables read-only analytical access to local CSV, Parquet, JSON files or a DuckDB database through MCP, with table discovery, column profiling, guarded SQL querying, and explain plans for safe use with Claude Desktop and Claude Code.
      8
      1
      MIT

    • universal-db-mcp

      joyous-coder
      A
      license
      B
      quality
      A
      maintenance
      Enables AI assistants to connect to 17+ databases and query/analyze data using natural language via MCP and HTTP APIs, supporting platforms like Claude Desktop, Cursor, and VS Code.
      42
      17 npm
      MIT

    • Chakra MCP Server

      EtnaLabs
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language queries and management of databases and subscribed data shares through Anthropic's Model Context Protocol.
      1
      MIT

    • syncly-dataset-mcp

      rimmade
      F
      license
      A
      quality
      D
      maintenance
      Enables querying JSON/JSONL social datasets in Claude Desktop via MCP tools, using DuckDB as the backend database.
      8
      -
    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

    A4.1/5.0

    Scored across 48 tools

    Disambiguation4/5

    Tools are scoped to distinct resource+action pairs (run-query vs query-format, insert-json vs insert-from-url, pause-cluster vs resume-cluster), and each description carries explicit 'NOT for' guidance that resolves most overlap. The remaining risk is inventory-style adjacency: list-organizations/list-clusters/list-databases/list-tables/list-logs/list-saved-queries/list-apps all read alike, and verify-cluster-s3-access vs verify-database-s3-access differ only by scope, so a careless agent could pick the wrong one in a long 48-tool list.

    Naming Consistency5/5

    Every name is kebab-case verb_noun with a predictable resource noun (list-tables, describe-table, create-workflow, update-organization-member, set-connector-status). Sub-resources are handled consistently with hyphenated qualifiers (insert-from-url, get-connector-metrics, verify-database-s3-access).

    Tool Count2/5

    48 tools is well beyond a comfortable selection surface for a single MCP endpoint, spanning data plane (query/insert/tables/logs), control plane (clusters, databases, S3 verification), IAM (keys, org members), workflows, Kafka connectors, and apps. Each grouping is internally coherent, but the full set is too heavy for an agent to scan reliably and would be better split into scoped servers or trimmed.

    Completeness4/5

    Core lifecycles are covered end-to-end: tables (list/describe/create/update/delete + insert paths), clusters (list/sizes/create/get/update/pause/resume), workflows (full CRUD), organizations, API keys, and apps. Gaps exist around connectors — no delete-connector or remove-connector-destination, only add — and no database update/delete-by-metadata or pending-invitation management, which agents will hit in admin workflows.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources