Skip to main content
Glama
cceniam

rf-log-mcp

by cceniam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to rf-log-mcp

No user-submitted related servers found.

    Related Servers

    • robocop-mcp

      aaltat
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that helps resolve Robocop static code analysis errors and warnings via LLM, providing tools to get reports and run format.
      11
      MIT

    • RobotMCP

      manykarim
      A
      license
      B
      quality
      A
      maintenance
      RobotMCP is a comprehensive Model Context Protocol (MCP) server that bridges the gap between human language and Robot Framework automation. It enables AI agents to understand test intentions, execute steps interactively, and generate complete test suites from successful executions.
      19
      2,831 PyPI
      117
      Apache 2.0

    • log-mcp

      ascii766164696D
      A
      license
      A
      quality
      D
      maintenance
      MCP server for log file analysis. Gives LLMs the ability to efficiently analyze large log files without loading them into context.
      7
      100
      MIT

    • QA Copilot AI

      Sham-coder16
      F
      license
      B
      quality
      B
      maintenance
      MCP server for AI-powered QA analysis. It enables analyzing test failures, identifying root causes, suggesting fixes, classifying defects, detecting flaky tests, and generating test cases and bug reports.
      10
      -

    • AI Test Pilot

      Drzymek92
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that generates, runs, and triages tests by introspecting Python modules or web pages, using structured LLM outputs for scenario generation and failure analysis.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_view retrieves a specific view, parse_result processes and indexes files, and search_messages queries indexed messages. There is no overlap in functionality, and the descriptions clearly differentiate their roles, making misselection unlikely.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (get_view, parse_result, search_messages) with clear, descriptive verbs and nouns. The naming is uniform throughout, using snake_case consistently without any deviations or mixed conventions.

    Tool Count3/5

    With only 3 tools, the set feels thin for a Robot Framework log management server, as it might lack operations like updating or deleting parsed data. However, the tools cover core parsing and querying functions, making it borderline appropriate but potentially limited in scope.

    Completeness3/5

    The tools provide basic parsing and search capabilities, but there are notable gaps: no update or delete operations for indexed data, and no tools for managing multiple runs or views beyond retrieval. This could lead to dead ends in workflows requiring data modification or broader management.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources