Skip to main content
Glama
log-10x

Log10x MCP Server

Official
by log-10x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Log10x MCP Server

No user-submitted related servers found.

    Related Servers

    • finops-mcp

      motoraif
      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

    • Kibana MCP Server

      gaharivatsa
      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
      -
    • @originchain/telemetry-mcp by originchain-ai

      @originchain/telemetry-mcpofficial

      originchain-ai
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to query OriginChain's telemetry agent for log patterns, semantic incident analysis, distributed traces, service graphs, and read-only SQL queries over telemetry data.
      10
      75 npm
      MIT

    • FOCUS MCP Server

      glassity
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to analyze cloud billing data in FOCUS format through natural language queries. Provides 36+ predefined cost analysis queries, custom SQL execution, and schema documentation for multi-cloud cost optimization and FinOps practices.
      11
      Apache 2.0
    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.1/5.0

    Scored across 55 tools

    Disambiguation3/5

    Tool names and descriptions establish distinct boundaries, but several clusters genuinely overlap: log10x_savings vs log10x_estimate_savings vs log10x_commitment_report, the retriever family (query/series/probe/query_status), the POC family (from_local/from_siem_submit/from_siem_status), and multiple 'what changed' tools (top_patterns/whats_changing/whats_new/pattern_diff). The verbose routing hints embedded in descriptions (e.g. 'call X not Y') actually confirm that selection is error-prone and requires careful reading rather than being self-evident.

    Naming Consistency5/5

    Every tool uses the uniform log10x_ prefix plus a consistent snake_case verb_noun or verb_noun_qualifier pattern (log10x_retriever_query, log10x_pattern_trend, log10x_compile_status). No camelCase or mixed conventions anywhere. Naming is fully predictable.

    Tool Count2/5

    At 55 tools this is well past the heavy threshold and forces the agent to carry a very large surface for one server, with many near-siblings that only differ by nuance. While the broad platform scope (install, signin, cost, retrieval, compile, cross-pillar, POC) means each tool maps to some real capability, the count is still excessive and several tools could be merged.

    Completeness4/5

    Coverage is genuinely broad and closed-loop: sign-in/out lifecycle, env validation and diffing, install/discovery advisors, cost attribution and mitigation, retrieval/rehydration, compile, and cross-pillar correlation all have entry points with status/poll companions. Minor gaps exist (e.g. no true delete/teardown for some artifacts, some backends explicitly deferred), but the surface covers the stated domain well.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources