Skip to main content
Glama
loggy-dev

@loggydev/mcp-server

by loggy-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to @loggydev/mcp-server

No user-submitted related servers found.

    Related Servers

    • Drumbeats MCP by drumbeats-io

      Drumbeats MCPofficial

      drumbeats-io
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Drumbeats monitoring. Enables creating monitors, triaging incidents, and running HTTP/SSL/DNS checks using natural language from any AI client.
      16
      10
      2
      Apache 2.0
    • uptrack-mcp by Uptrack-App

      uptrack-mcpofficial

      Uptrack-App
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Uptrack uptime monitoring. Manage monitors and incidents from AI agents like Claude, ChatGPT, and Cursor.
      12
      MIT

    • exit1-mcp

      Mopra
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Exit1 uptime monitoring. Enables AI assistants to create and manage uptime checks, configure alerts, and query status via natural language.
      32
      MIT

    • loki-mcp-server

      mo-silent
      F
      license
      Not graded
      quality
      F
      maintenance
      An MCP server that enables AI assistants to query and analyze logs from Grafana Loki using LogQL, supporting label discovery and keyword search.
      4
      -
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action, such as feature flags, heartbeats, status pages, uptime monitors, projects, and alerts. There is no ambiguity between tools.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using snake_case (e.g., create_uptime_monitor, list_feature_flags). Naming is predictable and uniform.

    Tool Count5/5

    15 tools is well within the typical 3-15 range for a server covering multiple domains like monitoring and feature flags. Each tool serves a clear purpose.

    Completeness3/5

    The tool set covers basic CRUD for heartbeats and uptime monitors but lacks delete operations for feature flags and status pages. Also, projects only have a list operation, and alerts are only listable. Notable gaps exist.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources