Skip to main content
Glama
nichuan

zhenyun-pangun-mcp

by nichuan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to zhenyun-pangun-mcp

No user-submitted related servers found.

    Related Servers

    • OpenObserve MCP Server

      adarshba
      A
      license
      A
      quality
      C
      maintenance
      Enables querying logs, traces, and metrics from multiple OpenObserve instances via MCP tools, with parallel execution, batching, and caching.
      6
      46 npm
      11
      MIT

    • ops-mcp-kit

      1907670605
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query company logs, databases, caches, and config centers (e.g., Aliyun SLS, MySQL, Redis, Nacos) through local MCP servers, with read-only enforcement and SSH tunneling for production access.
      -

    • observability-mcp

      blue-sky-exist
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for querying observability data from Elasticsearch, SkyWalking, and Prometheus/VictoriaMetrics, enabling AI models to search logs, traces, and metrics across environments.
      9
      MIT

    • middle-tool

      2514385224
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides a unified MCP server to interact with multiple middleware (Loki, MySQL, Redis, RocketMQ, Elasticsearch, MongoDB) through a desktop application for connection management and configuration export.
      4
      MIT

    • Overwatch MCP

      malindarathnayake
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables querying logs and metrics from Graylog, Prometheus, and InfluxDB 2.x. It provides tools for executing Lucene log searches, PromQL queries, and Flux queries directly within MCP-compatible clients.
      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.4/5.0

    Scored across 17 tools

    Disambiguation5/5

    Each tool serves a distinct purpose within its domain: log query tools are clearly separated by data source (Loki vs. SLS) and environment, database tools cover different schema operations, and issue tools handle specific retrieval tasks. No two tools overlap in function.

    Naming Consistency4/5

    Most tools follow a consistent 'service_operation' pattern (e.g., obs_log_query, archery_query, choerodon_list_issue). The only deviation is 'search_repo' which lacks the service prefix, but it still uses a clear verb_noun format. Overall naming is predictable and readable.

    Tool Count4/5

    17 tools covering logging, database operations, issue tracking, and code search is on the higher side but justified given the diverse domains. Each tool serves a specific need, and the count is appropriate for the server's multi-purpose scope.

    Completeness2/5

    The tool surface is heavily read-oriented: logging and database tools allow querying but not modification. Issue tracking is particularly incomplete, lacking create, update, and delete operations. Agents will encounter dead ends when trying to perform standard CRUD workflows.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources