Skip to main content
Glama
ADIKANT

datalens-dev-mcp

by ADIKANT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to datalens-dev-mcp

No user-submitted related servers found.

    Related Servers

    • yadirect-mcp

      Lermont
      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

    • Semantic BI MCP

      LovroBubanic
      F
      license
      Not graded
      quality
      D
      maintenance
      Model Context Protocol (MCP) server that gives AI assistants a safe, correct data-analyst capability over business metrics - without raw SQL improvisation.
      -

    • Yandex Webmaster MCP

      askads
      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
      21 npm
      MIT

    • Superset MCP Server

      okybaguslukmana
      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.
      153 npm
      MIT

    • KubeWhisper

      abdulhusainahk
      A
      license
      Not graded
      quality
      C
      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
    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.3/5.0

    Scored across 25 tools

    Disambiguation5/5

    Each tool maps to a distinct DataLens operation (auth, object CRUD, validation, cleanup, admin), and descriptions clearly state bounded scope. Minor conceptual overlap between workbooks_list/workbook_entries and object_get/dashboard_snapshot is resolved by explicit wording.

    Naming Consistency4/5

    All tools use snake_case with a consistent dl_ prefix, mostly following dl_<resource>_<action>. A few entries use noun-first or verb-first ordering (dl_compile_recipe, dl_workbooks_list), but the set remains predictable.

    Tool Count3/5

    25 tools is heavy for a single MCP server and sits at the upper boundary where agents may struggle to scan capabilities. The functions are granular but could likely be consolidated without losing coverage.

    Completeness4/5

    The surface covers read, validate, create/update/publish, operations, cleanup, backup, and admin licensing, which is strong for DataLens development. Gaps include no direct single-object delete and no operation listing, though cleanup_apply and operation_get provide partial workarounds.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources