Skip to main content
Glama
miningyu

Scouter MCP Server

by miningyu

Related Servers

Alternatives to Scouter MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      A stdio MCP server that connects directly to a Scouter Collector over TCP and queries XLogs, counters, and objects. Its purpose is to let an AI quickly explore Scouter metrics and diagnose root causes.
      2
      Apache 2.0
    • -
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that bridges AI assistants with SQL databases, enabling natural language querying across multiple database types with built-in optimization and security.
      3
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives AI agents real-time observability into Apache Kafka clusters, enabling natural language queries for broker health, consumer lag, and diagnostics.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that enables AI assistants to query and manage Microsoft SQL Server databases using natural language.
      184 npm
      5
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server enables AI models to directly and securely query databases using persistent or temporary connections, supporting multiple data sources with automatic connection management.
      74 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives AI assistants direct access to SAP HANA performance data — query plans, execution stats, memory usage.
      MIT

    TDQS

    A4/5.0

    Scored across 25 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but a few pairs like get_realtime_xlogs vs get_raw_xlog and get_agent_info vs get_thread_dump could be confused at first glance. Descriptions are detailed enough to separate them, but the boundaries are not perfectly crisp.

    Naming Consistency4/5

    The vast majority of tools follow a get_<noun> pattern (e.g., get_system_overview, get_transaction_detail). Two tools deviate: diagnose_performance and lookup_text. This is a minor inconsistency, but the overall naming is predictable and readable.

    Tool Count4/5

    25 tools is on the heavier side, but the server covers a broad APM domain: transactions, services, SQL, errors, alerts, configuration, and raw data access. Each tool addresses a legitimate need, so the count feels justified rather than bloated.

    Completeness5/5

    The tool surface is remarkably complete for a performance monitoring server. It covers system overview, automated diagnosis, counter trends, transaction search and detail, distributed tracing, service analysis, SQL analysis, error analysis, visitor statistics, alerts, configuration reading, host/agent info, thread dumps, and raw data access. There are no obvious dead ends or missing core operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues