logflare-mcp
Related Servers
Alternatives to logflare-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Sumo Logic's REST APIs through MCP, allowing log search, dashboard management, metrics querying, collector and monitor operations.5MIT
- 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.25 npm-
- AlicenseNot gradedqualityCmaintenanceEnables connecting Postgres databases to MCP clients with built-in query and inspection tools, custom parametrized SQL tools, scoped API keys, group permissions, and audit logging.5MIT
- AlicenseNot gradedqualityBmaintenanceEnables incident responders to query and correlate observability and DevOps evidence across Grafana, Prometheus, Loki, Uptime Kuma, CloudWatch, IAM, and PostHog from a local MCP client, with bounded reads and redacted audit records.MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with InfluxDB v3 (Core/Enterprise/Cloud Dedicated) through MCP clients. Supports database management, data querying and writing, schema inspection, and token administration operations.430 npmMIT
- AlicenseNot gradedqualityDmaintenanceExposes configured log files as MCP tools, enabling agents to list, query, and follow logs from local and SSH sources.MIT
TDQS
Scored across 7 tools
Each tool targets a distinct operation: ad-hoc queries, saved endpoint execution, source retrieval, schema inspection, recent events, and listing. No two tools have overlapping purposes; descriptions clearly differentiate them.
All tool names follow a consistent verb_noun pattern with lowercase and underscores (e.g., execute_query, list_sources). The prefixes 'get', 'list', 'execute', and 'query' are uniformly used for similar actions.
With 7 tools, the server is well-scoped for a logging/query domain. Each tool serves a clear purpose without redundancy, and the count is neither too sparse nor overwhelming.
The tool set covers core operations: listing and inspecting sources, querying via ad-hoc SQL or saved endpoints, and fetching recent events. Missing create/update/delete for sources and endpoints, but these may be out of scope for a read-focused MCP server.