sumo-logic-mcp
Related Servers
Alternatives to sumo-logic-mcp
No user-submitted related servers found.
Related Servers
- FlicenseBqualityBmaintenanceMCP server that integrates with Sumo Logic's API to perform log searches, data discovery, metrics queries, and monitoring.157 npm-
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Sumo Logic's REST APIs through MCP, allowing log search, dashboard management, metrics querying, collector and monitor operations.5MIT
- AlicenseAqualityBmaintenanceA 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.56 npm1MIT
- AlicenseNot gradedqualityBmaintenanceMCP 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.3MIT
- FlicenseAqualityCmaintenanceRead-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.267 npm-
- -licenseBqualityNot gradedmaintenanceMCP 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.19 npm10-
TDQS
Scored across 48 tools
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.
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.
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.
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.