Skip to main content
Glama
mbe24

yokozuna-mcp

by mbe24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to yokozuna-mcp

No user-submitted related servers found.

    Related Servers

    • sumo-mcp-readonly

      CraigWetzelberger
      A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server for querying Sumo Logic logs, enabling AI assistants to search and investigate application logs with opinionated tools and secure credential handling.
      5
      6 npm
      1
      MIT

    • mcp-sumologic

      giftHEALTH
      F
      license
      B
      quality
      B
      maintenance
      MCP server that integrates with Sumo Logic's API to perform log searches, data discovery, metrics queries, and monitoring.
      15
      7 npm
      -

    • Log Reader MCP

      hassansaadfr
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that provides AI assistants with direct access to application logs for on-demand searching, filtering, and analysis. It enables tools like Cursor to summarize log entries and identify errors within the development environment to streamline debugging.
      8 npm
      6
      MIT

    • mcp-server-logs-sieve

      Oluwatunmise-olat
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that connects Claude (or any MCP compatible client) to your existing log infrastructure. Query, summarize, and trace logs in plain English across GCP Cloud Logging, AWS CloudWatch, Azure Log Analytics, Grafana Loki, and Elasticsearch without writing filter expressions or leaving your editor.
      12 npm
      3
      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

    A4.4/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, e.g., sumo_create_search_job vs sumo_run_search, but the latter is a higher-level wrapper that combines create, wait, and delete, which could cause confusion. However, descriptions are clear enough to differentiate.

    Naming Consistency5/5

    All tools follow a consistent 'sumo_verb_noun' pattern. Verbs like create, delete, get, list, describe, export, facets, trend, error_digest, new_since, run_search are all well-structured and predictable.

    Tool Count5/5

    14 tools is appropriate for the server's purpose—covering search job lifecycle, data retrieval, analysis, monitoring, and alerts. The number is neither too few nor excessive.

    Completeness4/5

    The tool set covers core workflows: job management, data retrieval, schema analysis, triage, trends, facets, monitors, and alerts. Missing are tools for creating/updating monitors or managing saved searches, but these are not essential for typical agent interaction.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources