Skip to main content
Glama
Tinker-LGD2026

CLS MCP Server

by Tinker-LGD2026
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to CLS MCP Server

No user-submitted related servers found.

    Related Servers

    • Tencent Cloud Log Service (CLS) MCP Server by Tencent

      Tencent Cloud Log Serviceofficial

      Tencent
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables large language models to directly access Tencent Cloud Log Service for log search, metric queries, and alarm management without code.
      271 npm
      14
      Apache 2.0

    • aliyun-sls-mcp

      SuxyEE
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to query and analyze Alibaba Cloud SLS logs using natural language, supporting multiple log sources like Function Compute and ECS. It provides tools for searching logs, performing SQL analysis, and visualizing log distributions directly within Cursor or Claude.
      6
      19 npm
      11
      MIT

    • Aliyun MCP Server

      nailuoGG
      A
      license
      B
      quality
      C
      maintenance
      A Claude integration tool that enables users to query and analyze Aliyun (Alibaba Cloud) Simple Log Service logs through natural language commands.
      1
      15 npm
      2
      GPL 2.0
    • Alibaba Cloud Observability MCP Server by aliyun

      Alibaba Cloud Observabilityofficial

      aliyun
      F
      license
      A
      quality
      B
      maintenance
      Provides tools for accessing Alibaba Cloud observability products including SLS (Log Service) and ARMS (Application Real-time Monitoring Service), allowing any MCP-compatible AI assistants to quickly interact with these services.
      9
      167
      -
    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/5.0

    Scored across 24 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific CLS resources like logs, alarms, metrics, or configurations, with clear boundaries. However, some potential confusion exists between cls_describe_alarm_detail and cls_get_alarm_detail, as both retrieve alarm details but through different mechanisms, which could lead to misselection if not carefully read.

    Naming Consistency5/5

    Tool names follow a highly consistent snake_case pattern with a 'cls_' prefix, using descriptive verbs like 'describe', 'get', 'search', 'list', 'query', and 'convert'. This uniformity makes the set predictable and easy to navigate, with no deviations in naming style across all 24 tools.

    Tool Count3/5

    With 24 tools, the count is on the higher side for a single server, bordering on heavy. While CLS is a comprehensive logging service, some tools like cls_describe_search_syntax (documentation) and cls_convert_time (utility) might be better integrated or reduced, making the surface feel slightly bloated but still manageable.

    Completeness5/5

    The tool set provides extensive coverage for CLS operations, including CRUD-like actions for logs, alarms, metrics, dashboards, and configurations. It supports full workflows from data ingestion to analysis, with no obvious gaps—tools for time conversion, syntax reference, and context retrieval fill critical needs, ensuring agents can handle most tasks without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources