Skip to main content
Glama
rajfirke

sumo-logic-mcp

by rajfirke

Related Servers

Alternatives to sumo-logic-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Sumo Logic's REST APIs through MCP, allowing log search, dashboard management, metrics querying, collector and monitor operations.
      5
      MIT
    • 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for the FortiMonitor v2 monitoring API. 241 tools across 33 modules covering server management, outage monitoring, maintenance windows, metrics, notifications, cloud monitoring, SNMP, dashboards, reporting, and more. Unofficial community project, not affiliated with Fortinet. Python, MIT license, Docker and local deployment supported.
      3
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      Read-only MCP server for searching migrated Papertrail logs via SolarWinds Observability API. Provides tools to list environments and perform bearer-authenticated log queries through stdio.
      2
      67 npm
      -
    • -
      license
      B
      quality
      Not graded
      maintenance
      MCP server for Akamai APIs. 198 tools covering Property Manager, Edge DNS, CPS, WAF, and reporting. Built with TypeScript, featuring modular architecture, comprehensive testing, and multi-account support. Make Akamai accessible to AI assistants.
      1
      9 npm
      10
      -

    TDQS

    A3.5/5.0

    Scored across 48 tools

    Disambiguation4/5

    Most tools have distinct purposes, but some potential overlap exists: get_active_alerts vs list_monitors with status filters, and resolve_alert vs disable_monitor could confuse agents. Overall, the descriptions clarify the boundaries well.

    Naming Consistency4/5

    The naming follows a mostly consistent verb_noun pattern with list_ for collections and get_ for single items, but there are exceptions like get_active_alerts (a list) and get_search_results (retrieval). The mixed use of list_ and get_ for similar operations is a minor inconsistency.

    Tool Count2/5

    At 48 tools, the set is far beyond the typical range and exceeds the 25+ threshold. While the platform is broad, this many tools creates significant selection overhead for agents.

    Completeness3/5

    The tool set covers core workflows like search, monitors, dashboards, and collectors, but has notable gaps: no update_source or delete_source, no create/update/delete for lookup tables, field extraction rules, or many listed resources. Many resources are read-only, which limits administrative use cases.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues