Skip to main content
Glama
ADIKANT

datalens-dev-mcp

by ADIKANT

Related Servers

Alternatives to datalens-dev-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      A local MCP server that connects Yandex Direct advertising reports and safe campaign creation to AI agents, enabling natural-language analytics and protected campaign setup.
      8
      2
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Model Context Protocol (MCP) server that gives AI assistants a safe, correct data-analyst capability over business metrics - without raw SQL improvisation.
      -
    • A
      license
      A
      quality
      A
      maintenance
      MCP server for the Yandex Webmaster API, enabling natural-language queries about site indexing, search queries, IKS, diagnostics, sitemaps, and external links, as well as actions like recrawling, from AI assistants such as Claude, Cursor, and Codex.
      20
      60 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for Apache Superset that enables AI models to manage dashboards, create charts with auto-detection, and execute SQL queries programmatically. It utilizes stateless HTTP transport to ensure compatibility with integration tools like Open WebUI.
      46 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An AI-DevOps MCP server that gives LLMs read-only-by-default access to Kubernetes clusters, Prometheus metrics, and GitHub Actions, enabling natural language queries about infrastructure status and safe write operations with previews.
      MIT

    TDQS

    B3.2/5.0

    Scored across 26 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but a few read/validation tools (dl_object_get, dl_dashboard_snapshot, dl_object_relations; dl_editor_validate, dl_dataset_validate) target overlapping resources or operations and could be confused. The detailed descriptions help, but subtle boundaries remain.

    Naming Consistency5/5

    All tools use a consistent dl_ prefix and snake_case with a predictable domain_action pattern. Minor variations like dl_workbooks_list versus dl_object_get do not break the overall convention.

    Tool Count3/5

    26 tools is heavy for an MCP server, and the granularity (separate auth check/refresh, cleanup preview/apply, operation get/reconcile) adds cognitive load. Each tool serves a distinct step, but the set is borderline over-scoped.

    Completeness4/5

    The surface covers core DataLens development workflows: auth, discovery, CRUD, validation, publishing, cleanup, backup, and admin. Minor gaps include no explicit generic delete (cleanup_apply requires a preview) and no chart execution/preview tool.

    Maintenance

    ActivityActive
    ResponsivenessNo issues