Skip to main content
Glama
Log10x MCP Server

Log10x MCP Server

Official

Related Servers

Alternatives to Log10x MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query multi-cloud cost and usage data through a uniform read-only toolset, including cost summaries, trends, budgets, forecasts, and optimization recommendations.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides seamless access to Kibana and Periscope logs through a unified API with KQL and SQL querying, AI-powered log analysis, and support for searching across 1.3+ billion logs in 9 indexes.
      1
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets AI assistants read Costfluent cloud cost data — costs over time, saved cost reports, budgets, anomalies, the savings queue, commitments and coverage, and Kubernetes efficiency — and, where an Owner allows it, create and change annotations, cost reports, budgets, cost alerts and dashboards. It runs locally over stdio on the API token you supply, offering only the tools the token's capabilities and the organization setting permit, and never deletes anything.
      Apache 2.0

    TDQS

    A4/5.0

    Scored across 56 tools

    Disambiguation3/5

    Many tools share closely overlapping purposes: top_patterns / whats_changing / whats_new / pattern_diff / pattern_trend all answer 'what are my patterns doing over time', resolve_batch and extract_templates both run local templatization, and the three retriever_query/series/query_status and three poc_* tools require careful reading to distinguish. The descriptions compensate heavily with explicit 'call this first', 'do NOT call for X, use Y' routing cues, which keeps it workable but demonstrates the boundaries are genuinely fuzzy.

    Naming Consistency4/5

    Every tool carries the log10x_ prefix and uses snake_case throughout with a mostly predictable verb_noun pattern (resolve_batch, discover_env, configure_engine, retriever_query). A few noun-only names (doctor, start, baseline, savings) are minor deviations that don't break readability.

    Tool Count2/5

    56 tools is far beyond what a coherent set should expose; many are narrow single-purpose helpers (env_validate, env_diff_vs_envvars, compile_status, query_status, retriever_probe) that could be consolidated into parameterized tools. The sheer breadth makes the surface hard to navigate even though each tool is individually motivated.

    Completeness4/5

    Coverage is impressively broad for the domain: discovery, install, POC (networked/local/fenced), pattern analytics, mitigation, retrieval, cross-pillar correlation, and auth are all present. Gaps are minor, e.g. there is no obvious tool for deleting/cleaning up an offload bucket or revoking credentials, but agents can work around these.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues